Beam Failure Recovery of a Secondary Cell

ABSTRACT

Beam failure recovery (BFR) procedures for wireless communications are described. When beam failures occur on secondary cells, wireless devices may trigger a BFR procedure via an uplink resource for BFR. If a beam failure occurs for a secondary cell at a time that a wireless device does not have an uplink resource for BFR, the wireless device may perform one or more other actions for BFR of the secondary cell.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 17/591,331, filed Feb. 2, 2022, which is acontinuation of U.S. patent application Ser. No. 16/671,784, filed Nov.1, 2019 (now U.S. Pat. No. 11,283,674), which claims the benefit of U.S.Provisional Application No. 62/754,125, filed Nov. 1, 2018, each ofwhich is hereby incorporated by reference in its entirety.

BACKGROUND

Wireless communications may use one or more beams and/or other wirelessresources. A base station and/or a wireless device may experience afailure of one or more beams. A beam failure recovery procedure may berequired in response to a failure of one or more beams.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Wireless devices may use a beam failure recovery (BFR) procedure toaddress one or more beam failures. A base station may configure awireless device with uplink scheduling request resources for an activebandwidth part (BWP) of a primary cell that does not have BFR resources.The wireless device may use the uplink scheduling request resourcesduring a BFR procedure for a secondary cell, for example, if thewireless device does not have BFR uplink resources configured.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16A, FIG. 16B and FIG. 16C show examples of MAC subheaders.

FIG. 17A and FIG. 17B show examples of MAC PDUs.

FIG. 18A and FIG. 18B show examples of logical channel identifiers(LCIDs) for DL-SCH and LCIDs for UL-SCH.

FIG. 19A and FIG. 19B show examples of secondary cell (SCell)Activation/Deactivation MAC CE.

FIG. 20A and FIG. 20B show examples of beam failure scenarios.

FIG. 21 shows an example of a BFR procedure.

FIG. 22 shows an example of downlink BFR indication.

FIG. 23 shows an example of a BWP linkage in BFR procedure.

FIG. 24 shows an example of BWP configurations for BFR procedure.

FIG. 25A and FIG. 25B show examples of active BWP configurationscenarios for a BFR procedure for a secondary cell.

FIG. 26 shows an example of an active BWP configuration scenario fordownlink BFR procedure for a secondary cell.

FIG. 27 shows an example of timing of a downlink BFR procedure for asecondary cell.

FIG. 28A and FIG. 28B show examples of BWP switching during a downlinkBFR procedure for a secondary cell.

FIG. 29 shows an example of a downlink BFR procedure of a secondarycell.

FIG. 30 shows an example of SCell BFR procedure using dedicated BFRresources.

FIG. 31 shows an example of SCell BFR procedure using SR resources.

FIG. 32 shows an example of SCell BFR procedure using an SRconfiguration with fields indicating dedicated SR resources for BFR.

FIG. 33 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto beam failure recovery procedures in multicarrier communicationsystems.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

3GPP 3rd Generation Partnership Project

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

AS Access Stratum

ASIC Application-Specific Integrated Circuit

BA Bandwidth Adaptation

BCCH Broadcast Control Channel

BCH Broadcast Channel

BFR Beam Failure Recovery

BLER Block Error Rate

BPSK Binary Phase Shift Keying

BSR Buffer Status Report

BWP Bandwidth Part

CA Carrier Aggregation

CC Component Carrier

CCCH Common Control CHannel

CDMA Code Division Multiple Access

CN Core Network

CORESET Control Resource Set

CP Cyclic Prefix

CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex

C-RNTI Cell-Radio Network Temporary Identifier

CS Configured Scheduling

CSI Channel State Information

CSI-RS Channel State Information-Reference Signal

CQI Channel Quality Indicator

CSS Common Search Space

CU Central Unit

DC Dual Connectivity

DCCH Dedicated Control Channel

DCI Downlink Control Information

DL Downlink

DL-SCH Downlink Shared CHannel

DM-RS DeModulation Reference Signal

DRB Data Radio Bearer

DRX Discontinuous Reception

DTCH Dedicated Traffic Channel

DU Distributed Unit

EPC Evolved Packet Core

E-UTRA Evolved UMTS Terrestrial Radio Access

E-UTRAN Evolved-Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex

FPGA Field Programmable Gate Arrays

F1-C F1-Control plane

F1-U F1-User plane

gNB next generation Node B

HARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages

IE Information Element

IP Internet Protocol

LCH Logical Channel

LCID Logical Channel Identifier

LTE Long Term Evolution

MAC Medium Access Control

MCG Master Cell Group

MCS Modulation and Coding Scheme

MeNB Master evolved Node B

MIB Master Information Block

MME Mobility Management Entity

MN Master Node

NACK Negative Acknowledgement

NAS Non-Access Stratum

NG CP Next Generation Control Plane

NGC Next Generation Core

NG-C NG-Control plane

ng-eNB next generation evolved Node B

NG-U NG-User plane

NR New Radio

NR MAC New Radio MAC

NR PDCP New Radio PDCP

NR PHY New Radio PHYsical

NR RLC New Radio RLC

NR RRC New Radio RRC

NSSAI Network Slice Selection Assistance Information

O&M Operation and Maintenance

OFDM Orthogonal Frequency Division Multiplexing

PBCH Physical Broadcast CHannel

PCC Primary Component Carrier

PCCH Paging Control CHannel

PCell Primary Cell

PCH Paging CHannel

PDCCH Physical Downlink Control CHannel

PDCP Packet Data Convergence Protocol

PDSCH Physical Downlink Shared CHannel

PDU Protocol Data Unit

PHICH Physical HARQ Indicator CHannel

PHY PHYsical

PLMN Public Land Mobile Network

PMI Precoding Matrix Indicator

PRACH Physical Random Access CHannel

PRB Physical Resource Block

PSCell Primary Secondary Cell

PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal

PUCCH Physical Uplink Control CHannel

PUSCH Physical Uplink Shared CHannel

QAM Quadrature Amplitude Modulation

QCLed Quasi-Co-Located

QCL Quasi-Co-Location

QFI Quality of Service Indicator

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access CHannel

RAN Radio Access Network

RAT Radio Access Technology

RA-RNTI Random Access-Radio Network Temporary Identifier

RB Resource Blocks

RBG Resource Block Groups

RI Rank indicator

RLC Radio Link Control

RLM Radio Link Monitoring

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Signal Received Power

SCC Secondary Component Carrier

SCell Secondary Cell

SCG Secondary Cell Group

SC-FDMA Single Carrier-Frequency Division Multiple Access

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SeNB Secondary evolved Node B

SFN System Frame Number

S-GW Serving GateWay

SI System Information

SIB System Information Block

SINR Signal-to-Interference-plus-Noise Ratio

SMF Session Management Function

SN Secondary Node

SpCell Special Cell

SR Scheduling Request

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSB Synchronization Signal Block

SSS Secondary Synchronization Signal

sTAG secondary Timing Advance Group

TA Timing Advance

TAG Timing Advance Group

TAI Tracking Area Identifier

TAT Time Alignment Timer

TB Transport Block

TC-RNTI Temporary Cell-Radio Network Temporary Identifier

TCI Transmission Configuration Indication

TDD Time Division Duplex

TDMA Time Division Multiple Access

TRP Transmission and Receiving Point

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UL-SCH Uplink Shared CHannel

UPF User Plane Function

UPGW User Plane Gateway

VHDL VHSIC Hardware Description Language

Xn-C Xn-Control plane

Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, 1024-QAM and/or the like. Physical radio transmission may beenhanced by dynamically or semi-dynamically changing the modulation andcoding scheme, for example, depending on transmission requirementsand/or radio conditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface. The wirelessdevices 110A and/or 110B may be structurally similar to wireless devicesshown in and/or described in connection with other drawing figures. TheNode B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120Dmay be structurally similar to Nodes B and/or base stations shown inand/or described in connection with other drawing figures.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNB s 120A and 120B) and/or oneor more second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Medium Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. Mapping restrictions in alogical channel prioritization may control which numerology and/ortransmission timing a logical channel may use. An RLC sublayer maysupport transparent mode (TM), unacknowledged mode (UM), and/oracknowledged mode (AM) transmission modes. The RLC configuration may beper logical channel with no dependency on numerologies and/orTransmission Time Interval (TTI) durations. Automatic Repeat Request(ARQ) may operate on any of the numerologies and/or TTI durations withwhich the logical channel is configured. Services and functions of thePDCP layer for the user plane may comprise, for example, sequencenumbering, header compression and decompression, transfer of user data,reordering and duplicate detection, PDCP PDU routing (e.g., such as forsplit bearers), retransmission of PDCP SDUs, ciphering, deciphering andintegrity protection, PDCP SDU discard, PDCP re-establishment and datarecovery for RLC AM, and/or duplication of PDCP PDUs. Services and/orfunctions of SDAP may comprise, for example, mapping between a QoS flowand a data radio bearer. Services and/or functions of SDAP may comprisemapping a Quality of Service Indicator (QFI) in DL and UL packets. Aprotocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel. Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCID for alogical channel and/or MAC CE may be configured for the wireless deviceby the base station. The MAC sub-header corresponding to a MAC CE and/ora MAC SDU may comprise an LCID associated with the MAC CE and/or the MACSDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands. The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MAC CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs that indicate one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by 5GC; paging for mobile terminateddata area managed by 5GC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterinformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signaling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6 , FIG. 7A, FIG. 7B,FIG. 8 , and associated text, described below.

Other nodes in a wireless network (e.g., AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel. A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RSsymbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be less than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel. The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SS/PBCH blocks, forexample, if the downlink CSI-RS 522 and SS/PBCH blocks are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are outside of the PRBs configured for the SS/PBCH blocks.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loadedDM-RSsymbols for PDSCH 514. A DM-RS configuration may support one ormore DM-RS ports. A DM-RS configuration may support at least 8orthogonal downlink DM-RS ports, for example, for single user-MIMO.ADM-RS configuration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time, as well asan example frame structure, for a carrier. A multicarrier OFDMcommunication system may include one or more carriers, for example,ranging from 1 to 32 carriers (such as for carrier aggregation) orranging from 1 to 64 carriers (such as for dual connectivity). Differentradio frame structures may be supported (e.g., for FDD and/or for TDDduplex mechanisms). FIG. 6 shows an example frame timing. Downlink anduplink transmissions may be organized into radio frames 601. Radio frameduration may be 10 milliseconds (ms). A 10 ms radio frame 601 may bedivided into ten equally sized subframes 602, each with a 1 ms duration.Subframe(s) may comprise one or more slots (e.g., slots 603 and 605)depending on subcarrier spacing and/or CP length. For example, asubframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz and 480 kHzsubcarrier spacing may comprise one, two, four, eight, sixteen andthirty-two slots, respectively. In FIG. 6 , a subframe may be dividedinto two equally sized slots 603 with 0.5 ms duration. For example, 10subframes may be available for downlink transmission and 10 subframesmay be available for uplink transmissions in a 10 ms interval. Othersubframe durations such as, for example, 0.5 ms, 1 ms, 2 ms, and 5 msmay be supported. Uplink and downlink transmissions may be separated inthe frequency domain. Slot(s) may include a plurality of OFDM symbols604. The number of OFDM symbols 604 in a slot 605 may depend on thecyclic prefix length. A slot may be 14 OFDM symbols for the samesubcarrier spacing of up to 480 kHz with normal CP. A slot may be 12OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP.A slot may comprise downlink, uplink, and/or a downlink part and anuplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHaddressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CSresources. The DCI may comprise parameters indicating that the downlinkgrant is a CS grant. The CS grant may be implicitly reused according tothe periodicity defined by the one or more RRC messages. The CS grantmay be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) DCI via a PDCCH addressed to a CS-RNTI to activatethe CS resources. The DCI may comprise parameters indicating that theuplink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC message, TheCS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more transport blocks. TheDCI may indicate a downlink assignment indicating parameters forreceiving one or more transport blocks. The DCI may be used by the basestation to initiate a contention-free random access at the wirelessdevice. The base station may send (e.g., transmit) DCI comprising a slotformat indicator (SFI) indicating a slot format. The base station maysend (e.g., transmit) DCI comprising a preemption indication indicatingthe PRB(s) and/or OFDM symbol(s) in which a wireless device may assumeno transmission is intended for the wireless device. The base stationmay send (e.g., transmit) DCI for group power control of the PUCCH, thePUSCH, and/or an SRS. DCI may correspond to an RNTI. The wireless devicemay obtain an RNTI after or in response to completing the initial access(e.g., C-RNTI). The base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI, etc.). The wireless device may determine (e.g., compute)an RNTI (e.g., the wireless device may determine the RA-RNTI based onresources used for transmission of a preamble). An RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). The wireless device maymonitor a group common search space which may be used by the basestation for sending (e.g., transmitting) DCIs that are intended for agroup of wireless devices. A group common DCI may correspond to an RNTIwhich is commonly configured for a group of wireless devices. Thewireless device may monitor a wireless device-specific search space. Awireless device specific DCI may correspond to an RNTI configured forthe wireless device.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel. Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel. The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain. In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a CORESETs for at least one common search space. Foroperation on the PCell, one or more higher layer parameters may indicateat least one initial UL BWP for a random access procedure. If a wirelessdevice is configured with a secondary carrier on a primary cell, thewireless device may be configured with an initial BWP for random accessprocedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base station may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may not configure awireless device without a common search space on a PCell, or on aPSCell, in an active DL BWP. For an UL BWP in a set of one or more ULBWPs, a base station may configure a wireless device with one or moreresource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided a default DL BWP, a default BWP may be an initialactive DL BWP.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. 10 shows an example of three BWPs configured, BWP1(1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1118).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be de-activated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice. A master base station may determine (e.g., based on receivedmeasurement reports, traffic conditions, and/or bearer types) to requesta secondary base station to provide additional resources (e.g., servingcells) for a wireless device. After or upon receiving a request from amaster base station, a secondary base station may create and/or modify acontainer that may result in a configuration of additional serving cellsfor a wireless device (or decide that the secondary base station has noresource available to do so). For a wireless device capabilitycoordination, a master base station may provide (e.g., all or a part of)an AS configuration and wireless device capabilities to a secondary basestation. A master base station and a secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried via Xn messages. Asecondary base station may initiate a reconfiguration of the secondarybase station existing serving cells (e.g., PUCCH towards the secondarybase station). A secondary base station may decide which cell is aPSCell within a SCG. A master base station may or may not change contentof RRC configurations provided by a secondary base station. A masterbase station may provide recent (and/or the latest) measurement resultsfor SCG cell(s), for example, if an SCG addition and/or an SCG SCelladdition occurs. A master base station and secondary base stations mayreceive information of SFN and/or subframe offset of each other from anOAM and/or via an Xn interface (e.g., for a purpose of DRX alignmentand/or identification of a measurement gap). Dedicated RRC signaling maybe used for sending required system information of a cell as for CA, forexample, if adding a new SCG SCell, except for an SFN acquired from anMIB of a PSCell of a SCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a MAC entity, and/or a beam failure indication may initiate arandom access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating an equivalent and/orsimilar contents of Msg1 1220 and Msg3 1240 of a four-step random accessprocedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for a beam failurerecovery request and corresponding PRACH resource(s) (e.g., if any), atime window to monitor RA response(s), a time window to monitorresponse(s) on a beam failure recovery request, and/or a contentionresolution timer.

The Msg1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for a beam failurerecovery request associated with at least one of SS blocks and/orCSI-RSs. A wireless device may select a random access preamble indexcorresponding to a selected SS block or a CSI-RS from a set of one ormore random access preambles for a beam failure recovery request, forexample, if at least one of the SS blocks with an RSRP above a firstRSRP threshold amongst associated SS blocks is available, and/or if atleast one of CSI-RSs with a RSRP above a second RSRP threshold amongstassociated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. The wireless device may select a random access preambleindex, for example, if a base station does not configure a wirelessdevice with at least one contention free PRACH resource associated withSS blocks or CSI-RS. The wireless device may select the at least one SSblock and/or select a random access preamble corresponding to the atleast one SS block, for example, if a base station configures thewireless device with one or more contention free PRACH resourcesassociated with SS blocks and/or if at least one SS block with a RSRPabove a first RSRP threshold amongst associated SS blocks is available.The wireless device may select the at least one CSI-RS and/or select arandom access preamble corresponding to the at least one CSI-RS, forexample, if a base station configures a wireless device with one or morecontention free PRACH resources associated with CSI-RSs and/or if atleast one CSI-RS with a RSRP above a second RSPR threshold amongst theassociated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected SS block, for example,if the wireless device selects an SS block and is configured with anassociation between one or more PRACH occasions and/or one or more SSblocks. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected CSI-RS, for example, ifthe wireless device selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs.The wireless device may send (e.g., transmit), to a base station, aselected random access preamble via a selected PRACH occasions. Thewireless device may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedrandom access preamble is sent (e.g., transmitted). The wireless devicemay not determine an RA-RNTI for a beam failure recovery request. Thewireless device may determine an RA-RNTI at least based on an index of afirst OFDM symbol, an index of a first slot of a selected PRACHoccasions, and/or an uplink carrier index for a transmission of Msg11220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230. The wireless device may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For a beamfailure recovery procedure, the base station may configure the wirelessdevice with a different time window (e.g., bfr-ResponseWindow) tomonitor response to on a beam failure recovery request. The wirelessdevice may start a time window (e.g., ra-ResponseWindow orbfr-ResponseWindow) at a start of a first PDCCH occasion, for example,after a fixed duration of one or more symbols from an end of a preambletransmission. If the wireless device sends (e.g., transmits) multiplepreambles, the wireless device may start a time window at a start of afirst PDCCH occasion after a fixed duration of one or more symbols froman end of a first preamble transmission. The wireless device may monitora PDCCH of a cell for at least one random access response identified bya RA-RNTI, or for at least one response to a beam failure recoveryrequest identified by a C-RNTI, at a time that a timer for a time windowis running.

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention-free random accessprocedure is triggered for a beam failure recovery request and if aPDCCH transmission is addressed to a C-RNTI. The wireless device maydetermine that the random access procedure is successfully completed,and may indicate a reception of an acknowledgement for a systeminformation request to upper layers, for example, if at least one randomaccess response comprises a random access preamble identifier. Thewireless device may stop sending (e.g., transmitting) remainingpreambles (if any) after or in response to a successful reception of acorresponding random access response, for example, if the wirelessdevice has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1240, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel. A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of a MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MACSDUs to one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). A MACentity may handle a random access process (e.g., Random Access Control1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4-stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station).

A base station may communicate with a wireless device via a wirelessnetwork using one or more technologies, such as new radio technologies(e.g., NR, 5G, etc.). The one or more radio technologies may comprise atleast one of: multiple technologies related to physical layer; multipletechnologies related to medium access control layer; and/or multipletechnologies related to radio resource control layer. Enhancing the oneor more radio technologies may improve performance of a wirelessnetwork. System throughput, and/or data rate of transmission, may beincreased. Battery consumption of a wireless device may be reduced.Latency of data transmission between a base station and a wirelessdevice may be improved. Network coverage of a wireless network may beimproved. Transmission efficiency of a wireless network may be improved.

A base station may send (e.g., transmit) DCI via a PDCCH for at leastone of: a scheduling assignment and/or grant; a slot formatnotification; a preemption indication; and/or a power-control command.The DCI may comprise at least one of: an identifier of a DCI format; adownlink scheduling assignment(s); an uplink scheduling grant(s); a slotformat indicator; a preemption indication; a power-control forPUCCH/PUSCH; and/or a power-control for SRS.

A downlink scheduling assignment DCI may comprise parameters indicatingat least one of: an identifier of a DCI format; a PDSCH resourceindication; a transport format; HARQ information; control informationrelated to multiple antenna schemes; and/or a command for power controlof the PUCCH. An uplink scheduling grant DCI may comprise parametersindicating at least one of: an identifier of a DCI format; a PUSCHresource indication; a transport format; HARQ related information;and/or a power control command of the PUSCH.

Different types of control information may correspond to different DCImessage sizes. Supporting multiple beams, spatial multiplexing in thespatial domain, and/or noncontiguous allocation of RB s in the frequencydomain, may require a larger scheduling message, in comparison with anuplink grant allowing for frequency-contiguous allocation. DCI may becategorized into different DCI formats. A DCI format may correspond to acertain message size and/or usage.

A wireless device may monitor (e.g., in common search space or wirelessdevice-specific search space) one or more PDCCH for detecting one ormore DCI with one or more DCI format. A wireless device may monitor aPDCCH with a limited set of DCI formats, for example, which may reducepower consumption. The more DCI formats that are to be detected, themore power may be consumed by the wireless device.

The information in the DCI formats for downlink scheduling may compriseat least one of: an identifier of a DCI format; a carrier indicator; afrequency domain resource assignment; a time domain resource assignment;a time resource allocation; a bandwidth part indicator; a HARQ processnumber; one or more MCS; one or more NDI; one or more RV; MIMO relatedinformation; a downlink assignment index (DAI); PUCCH resourceindicator; PDSCH-to-HARQ feedback timing indicator; a TPC for PUCCH; anSRS request; and/or padding (e.g., if necessary). The MIMO relatedinformation may comprise at least one of: a PMI; precoding information;a transport block swap flag; a power offset between PDSCH and areference signal; a reference-signal scrambling sequence; a number oflayers; antenna ports for the transmission; and/or a transmissionconfiguration indication (TCI).

The information in the DCI formats used for uplink scheduling maycomprise at least one of: an identifier of a DCI format; a carrierindicator; a bandwidth part indication; a resource allocation type; afrequency domain resource assignment; a time domain resource assignment;a time resource allocation; an MCS; an NDI; a phase rotation of theuplink DMRS; precoding information; a CSI request; an SRS request; anuplink index/DAI; a TPC for PUSCH; and/or padding (e.g., if necessary).

A base station may perform CRC scrambling for DCI, for example, beforetransmitting the DCI via a PDCCH. The base station may perform CRCscrambling by binary addition of multiple bits of at least one wirelessdevice identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, SP CSI C-RNTI, and/or TPC-SRS-RNTI) and the CRC bits ofthe DCI. The wireless device may check the CRC bits of the DCI, forexample, if detecting the DCI. The wireless device may receive the DCI,for example, if the CRC is scrambled by a sequence of bits that is thesame as the at least one wireless device identifier.

A base station may send (e.g., transmit) one or more PDCCH in differentCORESETs, for example, to support a wide bandwidth operation. A basestation may transmit one or more RRC messages comprising configurationparameters of one or more CORESETs. A CORESET may comprise at least oneof: a first OFDM symbol; a number of consecutive OFDM symbols; a set ofresource blocks; and/or a CCE-to-REG mapping. A base station may send(e.g., transmit) a PDCCH in a dedicated CORESET for particular purpose,for example, for beam failure recovery confirmation. A wireless devicemay monitor a PDCCH for detecting DCI in one or more configuredCORESETs, for example, to reduce the power consumption.

A base station may send (e.g., transmit) one or more MAC PDUs to awireless device. A MAC PDU may comprise a bit string that may be bytealigned (e.g., multiple of eight bits) in length. Bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. The bit string may be readfrom the left to right, and then, in the reading order of the lines. Thebit order of a parameter field within a MAC PDU may be represented withthe first and most significant bit in the leftmost bit, and with thelast and least significant bit in the rightmost bit.

A MAC SDU may comprise a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC SDU may be included in a MAC PDU, forexample, from the first bit onward. In an example, a MAC CE may be a bitstring that is byte aligned (e.g., multiple of eight bits) in length. AMAC subheader may be a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC subheader may be placed immediately infront of the corresponding MAC SDU, MAC CE, and/or padding. A MAC entitymay ignore a value of reserved bits in a DL MAC PDU.

A MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the oneor more MAC subPDUs may comprise at least one of: a MAC subheader only(e.g., including padding); a MAC subheader and a MAC SDU; a MACsubheader and a MAC CE; and/or a MAC subheader and padding. The MAC SDUmay be of variable size. A MAC subheader may correspond to a MAC SDU, aMAC CE, and/or padding.

A MAC subheader may comprise: an R field comprising one bit; an F fieldwith one bit in length; an LCID field with multiple bits in length; an Lfield with multiple bits in length, for example, if the MAC subheadercorresponds to a MAC SDU, a variable-sized MAC CE, and/or padding.

A MAC subheader may comprise an eight-bit L field. The LCID field mayhave six bits in length, and the L field may have eight bits in length.A MAC subheader may comprise a sixteen-bit L field. The LCID field maybe six bits in length, and the L field may be sixteen bits in length.

A MAC subheader may comprise: an R field with two bits in length; and anLCID field with multiple bits in length, when the MAC subheadercorresponds to a fixed sized MAC CE, or padding. The LCID field may havesix bits in length, and the R field may have two bits in length.

DL MAC PDU, multiple MAC CEs may be placed together. A MAC subPDUcomprising MAC CE may be placed before any MAC subPDU comprising a MACSDU, or a MAC subPDU comprising padding.

UL MAC PDU, multiple MAC CEs may be placed together. A MAC subPDUcomprising MAC CE may be placed after all MAC subPDU comprising a MACSDU. The MAC subPDU may be placed before a MAC subPDU comprisingpadding.

A MAC entity of a base station may send (e.g., transmit) to a MAC entityof a wireless device one or more MAC CEs. The one or more MAC CEs maycomprise at least one of: an SP ZP CSI-RS Resource SetActivation/Deactivation MAC CE; a PUCCH spatial relationActivation/Deactivation MAC CE; a SP SRS Activation/Deactivation MAC CE;a SP CSI reporting on PUCCH Activation/Deactivation MAC CE; a TCI StateIndication for UE-specific PDCCH MAC CE; a TCI State Indication forUE-specific PDSCH MAC CE; an Aperiodic CSI Trigger State SubselectionMAC CE; a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE;a wireless device (e.g., UE) contention resolution identity MAC CE; atiming advance command MAC CE; a DRX command MAC CE; a long DRX commandMAC CE; an SCell activation and/or deactivation MAC CE (e.g., 1 Octet);an SCell activation and/or deactivation MAC CE (e.g., 4 Octet); and/or aduplication activation and/or deactivation MAC CE. A MAC CE may comprisean LCID in the corresponding MAC subheader. Different MAC CEs may havedifferent LCID in the corresponding MAC subheader. An LCID with 111011in a MAC subheader may indicate a MAC CE associated with the MACsubheader is a long DRX command MAC CE.

The MAC entity of the wireless device may send (e.g., transmit), to theMAC entity of the base station, one or more MAC CEs. The one or more MACCEs may comprise at least one of: a short buffer status report (BSR) MACCE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grant confirmationMAC CE; a single entry power headroom report (PHR) MAC CE; a multipleentry PHR MAC CE; a short truncated BSR; and/or a long truncated BSR. AMAC CE may comprise an LCID in the corresponding MAC sub-header.Different MAC CEs may have different LCIDs in the corresponding MACsubheader. The LCID with 111011 in a MAC subheader may indicate a MAC CEassociated with the MAC subheader is a short-truncated command MAC CE.

Two or more component carriers (CCs) may be aggregated, for example, ina carrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit on one or more CCs, for example, depending oncapabilities of the wireless device. The CA may be supported forcontiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, forexample, if configured with CA. At (e.g., during) an RRC connectionestablishment, re-establishment and/or handover, a cell providing a NASmobility information may be a serving cell. At (e.g., during) an RRCconnection re-establishment and/or handover procedure, a cell providinga security input may be a serving cell. The serving cell may be referredto as a primary cell (PCell). A base station may send (e.g., transmit),to a wireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells), forexample, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/ordeactivation mechanism of an SCell for an efficient battery consumption,for example, if the base station and/or the wireless device isconfigured with CA. A base station may activate or deactivate at leastone of the one or more SCells, for example, if the wireless device isconfigured with one or more SCells. The SCell may be deactivated, forexample, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example,after or in response to receiving an SCell activation and/ordeactivation MAC CE. A base station may send (e.g., transmit), to awireless device, one or more messages comprising ansCellDeactivationTimer timer. The wireless device may deactivate anSCell, for example, after or in response to an expiry of thesCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell activation/deactivation MAC CE activating anSCell. The wireless device may perform operations (e.g., after or inresponse to the activating the SCell) that may comprise: SRStransmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for theSCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring forthe SCell on the PCell; and/or PUCCH transmissions on the SCell.

The wireless device may start and/or restart a timer (e.g., ansCellDeactivationTimer timer) associated with the SCell, for example,after or in response to activating the SCell. The wireless device maystart the timer (e.g., sCellDeactivationTimer timer) in the slot, forexample, if the SCell activation/deactivation MAC CE has been received.The wireless device may initialize and/or re-initialize one or moresuspended configured uplink grants of a configured grant Type 1associated with the SCell according to a stored configuration, forexample, after or in response to activating the SCell. The wirelessdevice may trigger a PHR, for example, after or in response toactivating the SCell.

The wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell activation/deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a timer (e.g., ansCellDeactivationTimer timer) associated with an activated SCellexpires. The wireless device may stop the timer (e.g.,sCellDeactivationTimer timer) associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may stop a BWP inactivity timer associated with theactivated SCell, for example, after or in response to deactivating theactivated SCell. The wireless device may deactivate any active BWPassociated with the activated SCell, for example, after or in responseto deactivating the activated SCell. The wireless device may clear oneor more configured downlink assignments and/or one or more configureduplink grant Type 2 associated with the activated SCell, for example,after or in response to the deactivating the activated SCell. Thewireless device may suspend one or more configured uplink grant Type 1associated with the activated SCell, for example, after or in responseto deactivating the activated SCell. The wireless device may flush HARQbuffers associated with the activated SCell.

A wireless device may not perform certain operations, for example, if anSCell is deactivated. The wireless device may not perform one or more ofthe following operations if an SCell is deactivated: transmitting SRS onthe SCell; reporting CQI, PMI, RI, and/or CRI for the SCell on a PCell;transmitting on UL-SCH on the SCell; transmitting on a RACH on theSCell; monitoring at least one first PDCCH on the SCell; monitoring atleast one second PDCCH for the SCell on the PCell; and/or transmitting aPUCCH on the SCell.

A wireless device may restart a timer (e.g., an sCellDeactivationTimertimer) associated with the activated SCell, for example, if at least onefirst PDCCH on an activated SCell indicates an uplink grant or adownlink assignment. A wireless device may restart a timer (e.g., ansCellDeactivationTimer timer) associated with the activated SCell, forexample, if at least one second PDCCH on a serving cell (e.g. a PCell oran SCell configured with PUCCH, such as a PUCCH SCell) scheduling theactivated SCell indicates an uplink grant and/or a downlink assignmentfor the activated SCell. A wireless device may abort the ongoing randomaccess procedure on the SCell, for example, if an SCell is deactivatedand/or if there is an ongoing random access procedure on the SCell.

An SCell activation/deactivation MAC CE may comprise, for example, oneoctet. A first MAC PDU subheader comprising a first LCID may identifythe SCell activation/deactivation MAC CE of one octet. An SCellactivation/deactivation MAC CE of one octet may have a fixed size. TheSCell activation/deactivation MAC CE of one octet may comprise a singleoctet. The single octet may comprise a first number of C-fields (e.g.,seven) and a second number of R-fields (e.g., one).

An SCell Activation/Deactivation MAC CE may comprise, for example, anysize such as any quantity of octets (e.g., four octets). A second MACPDU subheader with a second LCID may identify the SCellActivation/Deactivation MAC CE of four octets. An SCellactivation/deactivation MAC CE of four octets may have a fixed size. TheSCell activation/deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g., 1). A C_(i) field mayindicate an activation/deactivation status of an SCell with an SCellindex i, for example, if an SCell with SCell index i is configured. AnSCell with an SCell index i may be activated, for example, if the C_(i)field is set to one. An SCell with an SCell index i may be deactivated,for example, if the C_(i) field is set to zero. The wireless device mayignore the C_(i) field, for example, if there is no SCell configuredwith SCell index i. An R field may indicate a reserved bit. The R fieldmay be set to zero.

A base station may configure a wireless device with one or moreTCI-States using and/or via a higher layer parameter, for example,PDSCH-Config for a serving cell. A number (e.g., quantity, plurality,etc.) of the one or more TCI-States may depend on a capability of thewireless device. The wireless device may use the one or more TCI-Statesto decode a PDSCH based on a detected PDCCH with a DCI. The DCI may beintended, for example, for the wireless device and/or the serving cell.Each of the one or more TCI-States state may contain one or moreparameters. The one or more parameters may be used, for example, toconfigure a quasi-co-location relationship between one or more downlinkreference signals (e.g., a first DL RS and/or a second DL RS) and theDM-RS ports of the PDSCH. The quasi-co-location relationship may beconfigured by a higher layer parameter QCL-Type1 for the first DL RS.The quasi-co-location relationship may be configured by a higher layerparameter QCL-Type2 for the second DL RS, for example, if the second DLRS is configured. Quasi co-location types (QCL-Types) associated withtwo DL RSs may not necessarily be the same, for example, if the one RSset contains a reference to the two DL RSs. The references of the two DLRSs may be, for example, to a same DL RS or to different DL RSs. TheQCL-Types corresponding to each DL RS may be indicated to the wirelessdevice by a higher layer parameter QCL-Type in parameter QCL-Info. Thehigher layer parameter QCL-Type may take at least one of the types:QCL-TypeA′: {Doppler shift, Doppler spread, average delay, delayspread}, QCL-TypeB′: {Doppler shift, Doppler spread}, QCL-TypeC′:{average delay, Doppler shift} and QCL-TypeD′: {Spatial Rx parameter}.

The wireless device may determine (e.g., assume) that one or more DM-RSports of a PDSCH of a serving cell are quasi-co-located with an SSB/PBCHblock, for example, (i) before the wireless device receives theactivation command and/or (ii) after the wireless device receives ahigher layer configuration of TCI-States. The SSB/PBCH block may bedetermined in an initial access procedure with respect to one or more ofQCL-TypeA′ and QCL-TypeD′, for example, if applicable.

A wireless device may be configured by a base station, with a higherlayer parameter TCI-PresentInDCI. The wireless device may determine(e.g., assume) that a TCI field is present in a DCI format (e.g., DCIformat 1_1) of a PDCCH transmitted on the CORESET, for example, if thehigher layer parameter TCI-PresentInDCI is set as ‘Enabled’ for aCORESET scheduling a PDSCH.

The wireless device may determine (e.g., assume) that one or more DM-RSports of a PDSCH of a serving cell are quasi-co-located with one or moreRS(s) in the TCI state with respect to QCL type parameter(s), forexample, if (i) the offset between reception of the DL DCI and thecorresponding PDSCH is less than the threshold Threshold-Sched-Offsetand/or if (ii) the higher layer parameter TCI-PresentInDCI is set to“Enabled” and the higher layer parameter TCI-PresentInDCI is notconfigured in RRC connected mode. The QCL type parameter(s) may be usedfor PDCCH quasi-co-location indication of the lowest CORESET-ID in thelatest slot. One or more CORESETs within an active BWP of the servingcell may be configured for the wireless device in the latest slot. Thewireless device may obtain the other QCL assumptions from the indicatedTCI states for its scheduled PDSCH, irrespective of a time offsetbetween the reception of the DL DCI and the corresponding PDSCH, if noneof the configured TCI states contains QCL-TypeD′.

A base station may send, to a wireless device, one or more configurationparameters. The one or more configuration parameters may indicate one ormore control resource sets (e.g., CORESETs). The one or moreconfiguration parameters may configure the one or more CORESETs. Thewireless device may be provided with the one or more (e.g., 2, 3, 4, 5,or any other quantity) configuration parameters via a higher layersignaling, for example, for a DL BWP configured to and/or for thewireless device in a serving cell. The wireless device may be provided,for a first CORESET of the one or more CORESETs and/or by a higher layerparameter (e.g., ControlResourceSet), at least one of: a CORESET index(e.g., by higher layer parameter controlResourceSetId), a DMRSscrambling sequence initialization value, a quantity (e.g., number,plurality, etc.) of consecutive symbols (e.g., by higher layer parameterduration), a set of resource blocks (e.g., by higher layer parameterfrequencyDomainResources), CCE-to-REG mapping parameters (e.g., byhigher layer parameter cce-REG-MappingType), an antenna portquasi-co-location parameter (e.g., by higher layer parameterTCI-States), or an indication of a presence or an absence of a TCI field(e.g., by higher layer parameter TCI-PresentInDCI). The antenna portquasi-co-location parameter may indicate, for example, quasi-co-locationinformation of a DM-RS antenna port for PDCCH reception in the firstCORESET.

A base station may indicate, to a wireless device, a TCI state for PDCCHreception for a CORESET of a serving cell by sending, for example, a TCIstate indication for a wireless device-specific PDCCH MAC CE. A wirelessdevice (e.g., a MAC entity of a wireless device) may indicate to lowerlayers (e.g., PHY) information regarding the TCI state indication forthe wireless device-specific PDCCH MAC CE, for example, if the wirelessdevice (e.g., MAC entity) receives a TCI state indication for thewireless device-specific PDCCH MAC CE on or for a serving cell.

A TCI state indication for the wireless device-specific PDCCH MAC CE maybe indicated (e.g., identified), for example, by a MAC PDU subheaderwith LCID. The TCI state indication for the wireless device-specificPDCCH MAC CE may have a fixed size (e.g., 16 bits, or any other quantityof bits, bytes, etc.) and/or may comprise one or more fields. The one ormore fields may comprise, for example, a serving cell ID, a CORESET ID,a TCI state ID, and/or a reserved bit.

The serving cell ID may indicate, for example, an identity of a servingcell for which the TCI state indication for the wireless device-specificPDCCH MAC CE may apply. The length of the serving cell ID may be n bits(e.g., n=5 bits, or any other quantity of bits, bytes, etc.).

The CORESET ID may indicate, for example, a CORESET. The CORESET may beindicated (e.g., identified) and/or associated with a CORESET ID (e.g.,ControlResourceSetId). A length of the CORESET ID may be n bits (e.g.,n=4 bits, or any other quantity of bits, bytes, etc.). Although CORESETID is used as an example, one skilled in the relevant art recognizesthat indications provided and/or from CORESET ID and/or informationprovided and/or from CORESET ID can be made and/or provided (e.g.,indicated) by any field in any message.

The TCI state ID may indicate, for example, the TCI state indicated(e.g., identified) by TCI-StateId. The TCI state may be applicable tothe CORESET indicated (e.g., identified) by the CORESET ID. A length ofthe TCI state ID may be n4 bits (e.g., n=6 bits, or any other quantityof bits, bytes, etc.).

An information element (e.g., ControlResourceSet) may be used toconfigure a time/frequency CORESET that may be searched for downlinkcontrol information. An information element (e.g., TCI-State) mayassociate one or more DL reference signals with a correspondingquasi-co-location (QCL) type. The information element (e.g., TCI-State)may comprise, for example, one or more fields, such as, for example,TCI-StateId and/or QCL-Info. The QCL-Info may comprise one or morefields. The one or more fields of QCL-Info may comprise, for example,one or more of: a serving cell index, BWP ID, a reference signal index(e.g., SSB-index, NZP-CSI-RS-ResourceID), and/or a QCL Type (e.g.,QCL-typeA, QCL-typeB, QCL-typeC, QCL-typeD).

A reference signal associated with a reference signal index may belocated in a carrier that may be indicated by, for example, the servingcell index. The information element (e.g., TCI-State) may apply to aserving cell in which the information element (e.g., TCI-State) isconfigured, for example, if the serving cell index is absent in aninformation element (e.g., TCI-State). The reference signal may belocated in a second serving cell other than the serving cell in whichthe information element (e.g., TCI-State) is configured, for example, ifthe QCL-Type is configured as typeD.

A wireless device may trigger a SR for requesting an uplink resource(e.g., a UL-SCH resource), for example, based on the wireless devicehaving a new transmission. A base station (e.g., a gNB) may send (e.g.,transmit) to a wireless device at least one message comprisingparameters indicating zero, one, or more SR configurations. A SRconfiguration may comprise a set of uplink resources (e.g., PUCCHresource(s)) for a SR for one or more BWPs and/or for one or more cells.A PUCCH resource for a SR may be configured for a BWP. For example, onePUCCH resource for a SR may be configured for a BWP. One or more SRconfigurations may correspond to one or more logical channels. One ormore logical channels may be mapped to zero or one SR configurations.One or more logical channels may be configured by the at least onemessage. A SR configuration of a logical channel (LCH) that triggers abuffer status report (BSR) may be determined and/or assumed (e.g.,considered) to be a corresponding SR configuration for a triggered SR.

The at least one message, for one or more SR configurations, may furthercomprise one or more parameters indicating at least one of: a SRprohibit timer; a maximum quantity of SR transmissions; a parameterindicating a periodicity and offset of SR transmission; and/or a PUCCHresource. The SR prohibit timer may be a duration, for example, duringwhich the wireless device may be not allowed to send (e.g., transmit)the SR. A maximum quantity (e.g., number) of SR transmissions may be atransmission quantity (e.g., number) for which the wireless device maybe allowed to send (e.g., transmit) the SR.

An uplink resource (e.g., PUCCH resource) may be indicated (e.g.,identified) by: a frequency location (e.g., starting PRB), and/or anuplink format (e.g., PUCCH format) associated with initial cyclic shiftof a base sequence and time domain location (e.g., starting symbolindex). An uplink format (e.g., PUCCH format) may be PUCCH format 0, orPUCCH format 1, or PUCCH format 2, or PUCCH format 3, or PUCCH format 4.An uplink format (e.g., PUCCH format 0) may have a length of 1 or 2 OFDMsymbols or any other quantity of symbols. An uplink format (e.g., PUCCHformat 0, PUCCH format 1, etc.) may comprise a quantity of bits that maybe less than or equal to 2 bits or any other quantity of bits. An uplinkformat (e.g., PUCCH format 1) may occupy a quantity between 4 and 14 ofOFDM symbols or any other quantity of symbols. An uplink format (e.g.,PUCCH format 2) may occupy 1 or 2 OFDM symbols or any other quantity ofsymbols. An uplink format (e.g., PUCCH format 2, PUCCH format 3, PUCCHformat 4, etc.) may comprise a quantity of bits that may be greater than2 bits. An uplink format (e.g., PUCCH format 3) may occupy a quantitybetween 4 and 14 of OFDM symbols or any other quantity of symbols. Anuplink format (e.g., PUCCH format 4) may occupy a quantity between 4 and14 of OFDM symbols or any other quantity of symbols.

An uplink format (e.g., PUCCH format) for SR transmission may be a PUCCHformat 0, or PUCCH format 1. A wireless device may send (e.g., transmit)an uplink signal via an uplink resource (e.g., PUCCH via a PUCCHresource) for a corresponding SR configuration, for example, based onthe wireless device sending (e.g., transmitting) a positive SR. Awireless device may send (e.g., transmit) an uplink signal (e.g., PUCCH)by setting the cyclic shift to a first value (e.g., 0), for example,based on a positive SR transmission using PUCCH format 0. A wirelessdevice may send (e.g., transmit) an uplink signal (e.g., PUCCH) bysetting a first bit to a first value (e.g., 0), for example, before BPSKmodulated using a sequence and/or based on a positive SR transmissionusing PUCCH format 1.

A SR may be multiplexed with HARQ-ACK or CSI using an uplink format(e.g., PUCCH format). A wireless device may determine a cyclic shift ofthe base sequence, for example, based on a positive SR multiplexed withHARQ-ACK, the initial cyclic shift, and/or a first cyclic shift based onone or more values of one or more HARQ-ACK bits. A wireless device maydetermine a cyclic shift of the base sequence, for example, based on anegative SR multiplexed with HARQ-ACK, the initial cyclic shift, and/ora second cyclic shift. The second cyclic shift may be based on one ormore values of the one or more HARQ-ACK bits. The first cyclic shift maybe different from the second cyclic shift.

A wireless device may maintain a SR transmission counter (e.g.,SR_COUNTER) associated with a SR configuration. A wireless device mayset the SR transmission counter (e.g., SR_COUNTER) of the SRconfiguration to a first value (e.g., 0), for example, based on a SR ofa SR configuration being triggered, and/or no other SRs pendingcorresponding to a same SR configuration. A wireless device maydetermine and/or assume that (e.g., consider) the SR is pending until itis cancelled, for example, based on an SR being triggered. All pendingSR(s) may be cancelled, for example, based on one or more UL grantsaccommodating all pending data available for transmission. A wirelessdevice may determine one or more uplink resources (e.g., PUCCHresource(s)) of an active BWP as valid uplink resources (e.g., PUCCHresource(s)) before a time of a SR transmission occasion.

A wireless device may send (e.g., transmit) an uplink signal via anuplink resource (e.g., a PUCCH via a PUCCH resource) associated with aSR configuration, for example, based on the wireless device sending(e.g., transmitting) a positive SR. A wireless device may send (e.g.,transmit) the uplink signal using an uplink format (e.g., PUCCH usingPUCCH format 0, or PUCCH format 1), according to the uplinkconfiguration (e.g., PUCCH configuration).

A wireless device may receive one or more RRC message comprisingparameters of one or more SR configurations. The parameters, for one ormore of the one or more SR configurations, may indicate at least one of:a SR prohibit timer; a maximum quantity of SR transmissions; a parameterindicating a periodicity and offset of SR transmission; and/or an uplinkresource indicated (e.g., identified) by an uplink resource index (e.g.,PUCCH resource indicated (e.g., identified) by a PUCCH resource index).A wireless device may set a SR transmission counter (e.g., SR_COUNTER)to a first value (e.g., 0), if there is no other pending SRscorresponding to the SR configuration, for example, based on a SR of aSR configuration triggered (e.g., pending) based on a BSR beingtriggered on a LCH corresponding to the SR configuration.

A wireless device may determine whether there is at least one validuplink resource (e.g., PUCCH resource) for the pending SR, for example,before the time of a SR transmission occasion. The wireless device mayinitiate a random access procedure on a PCell, for example, based ondetermining that there is no valid PUCCH resource for the pending SR.The wireless device may cancel the pending SR, for example, based on orin response to determining that there is no valid uplink resource (e.g.,PUCCH resource) for the pending SR.

A wireless device may determine a SR transmission occasion on the atleast one valid uplink resource (e.g., PUCCH resource), for example,based on at least one valid uplink resource (e.g., PUCCH resource) forthe pending SR and/or a periodicity and an offset of SR transmission.The wireless device may wait for another SR transmission occasion, forexample, based on the SR prohibit timer running. The wireless device mayincrement the SR transmission counter (e.g., SR_COUNTER) (e.g., by one)and/or cause (e.g., instruct) the physical layer of the wireless deviceto indicate and/or signal the SR on the at least one valid uplinkresource (e.g., PUCCH resource) for the SR. The wireless device mayincrement the SR transmission counter and/or cause (e.g., instruct) thephysical later of the wireless device to indicate and/or signal the SRon the at least one valid uplink resource for the SR, for example, basedon: a determination that the SR prohibit timer is not running, and/or adetermination that the at least one valid uplink resource (e.g., PUCCHresource) for the SR transmission occasion is not overlapping with ameasurement gap. The wireless device may increment the SR transmissioncounter (e.g., SR_COUNTER) (e.g., by one) and/or cause (e.g., instruct)the physical layer of the wireless device to indicate and/or signal theSR on the at least one valid uplink resource (e.g., PUCCH resource) forthe SR, for example, based on: a determination that the at least onevalid uplink resource (e.g., PUCCH resource) for the SR transmissionoccasion is not overlapping with an uplink shared channel (UL-SCH)resource, and/or a determination that the SR transmission counter (e.g.,SR_COUNTER) is less than the maximum quantity of SR transmissions. Awireless device (e.g., a physical layer of the wireless device) may send(e.g., transmit) a PUCCH via the at least one valid uplink resource(e.g., PUCCH resource) for the SR. The wireless device may monitor anuplink channel (e.g., PDCCH) for detecting a DCI for uplink grant, forexample, based on or in response to sending (e.g., transmitting) theuplink signal (e.g., PUCCH).

The wireless device may cancel the pending SR and/or stop the SRprohibit timer, for example, based on receiving one or more uplinkgrants which may accommodate all pending data available fortransmission. The wireless device may repeat one or more actionscomprising: determining the at least one valid uplink resource (e.g.,PUCCH resource); checking whether the SR prohibit timer is running;determining that the SR transmission counter (e.g., SR_COUNTER) is equalor greater than the maximum quantity of SR transmissions; incrementingthe SR transmission counter (e.g., SR_COUNTER), sending (e.g.,transmitting) the SR, and/or starting the SR prohibit timer; and/ormonitoring an uplink channel (e.g., PDCCH) for an uplink grant. Thewireless device may repeat some or all of these actions, for example,based on the wireless device not receiving one or more uplink grantsthat accommodate pending data available for transmission.

A wireless device may release an uplink channel (e.g., PUCCH) for one ormore serving cells, release SRS for the one or more serving cells, clearone or more configured downlink assignments and uplink grants, initiatea random access procedure on a PCell, and/or cancel all the pending SRs,for example, based on the SR transmission counter (e.g., SR_COUNTER)indicating a quantity equal to or greater than the maximum quantity(e.g., number) of SR transmissions.

FIG. 16A shows an example of a MAC subheader comprising an eight-bit Lfield. The LCID field may have six bits in length. The L field may haveeight bits in length.

FIG. 16B shows an example of a MAC subheader with a sixteen-bit L field.The LCID field may have six bits in length. The L field may have sixteenbits in length. A MAC subheader may comprise: a R field comprising twobits in length; and an LCID field comprising multiple bits in length(e.g., if the MAC subheader corresponds to a fixed sized MAC CE), and/orpadding.

FIG. 16C shows an example of the MAC subheader. The LCID field maycomprise six bits in length, and the R field may comprise two bits inlength.

FIG. 17A shows an example of a DL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising MAC CE may be placed before anyMAC subPDU comprising a MAC SDU, and/or before a MAC subPDU comprisingpadding.

FIG. 17B shows an example of a UL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising a MAC CE may be placed afterall MAC subPDU comprising a MAC SDU. The MAC subPDU may be placed beforea MAC subPDU comprising padding.

FIG. 18A shows first examples of LCIDs. FIG. 18B shows second examplesof LCIDs. In each of FIG. 18A and FIG. 18B, the left columns compriseindices, and the right columns comprises corresponding LCID values foreach index.

FIG. 18A shows an example of an LCID that may be associated with the oneor more MAC CEs. A MAC entity of a base station may send (e.g.,transmit) to a MAC entity of a wireless device one or more MAC CEs. Theone or more MAC CEs may comprise at least one of: an SP ZP CSI-RSResource Set Activation/Deactivation MAC CE; a PUCCH spatial relationActivation/Deactivation MAC CE; a SP SRS Activation/Deactivation MAC CE;a SP CSI reporting on PUCCH Activation/Deactivation MAC CE; a TCI StateIndication for UE-specific PDCCH MAC CE; a TCI State Indication forUE-specific PDSCH MAC CE; an Aperiodic CSI Trigger State SubselectionMAC CE; a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE;a wireless device (e.g., UE) contention resolution identity MAC CE; atiming advance command MAC CE; a DRX command MAC CE; a long DRX commandMAC CE; an SCell activation and/or deactivation MAC CE (e.g., 1 Octet);an SCell activation and/or deactivation MAC CE (e.g., 4 Octet); and/or aduplication activation and/or deactivation MAC CE. A MAC CE may comprisean LCID in the corresponding MAC subheader. Different MAC CEs may havedifferent LCID in the corresponding MAC subheader. An LCID with 111011in a MAC subheader may indicate that a MAC CE associated with the MACsubheader is a long DRX command MAC CE.

FIG. 18B shows further examples of LCIDs associated with one or more MACCEs. The MAC entity of the wireless device may send (e.g., transmit), tothe MAC entity of the base station, one or more MAC CEs. The one or moreMAC CEs may comprise at least one of: a short buffer status report (BSR)MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grantconfirmation MAC CE; a single entry power headroom report (PHR) MAC CE;a multiple entry PHR MAC CE; a short truncated BSR; and/or a longtruncated BSR. A MAC CE may comprise an LCID in the corresponding MACsubheader. Different MAC CEs may have different LCIDs in thecorresponding MAC subheader. The LCID with 111011 in a MAC subheader mayindicate that a MAC CE associated with the MAC subheader is ashort-truncated command MAC CE.

Two or more component carriers (CCs) may be aggregated, for example, ina carrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit on one or more CCs, for example, depending oncapabilities of the wireless device. The CA may be supported forcontiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, forexample, if configured with CA. At (e.g., during) an RRC connectionestablishment, re-establishment and/or handover, a cell providing a NASmobility information may be a serving cell. At (e.g., during) an RRCconnection re-establishment and/or handover procedure, a cell providinga security input may be a serving cell. The serving cell may be referredto as a primary cell (PCell). A base station may send (e.g., transmit),to a wireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells), forexample, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/ordeactivation mechanism of an SCell for an efficient battery consumption,for example, if the base station and/or the wireless device isconfigured with CA. A base station may activate or deactivate at leastone of the one or more SCells, for example, if the wireless device isconfigured with one or more SCells. The SCell may be deactivated, forexample, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example,after or in response to receiving an SCell activation and/ordeactivation MAC CE. A base station may send (e.g., transmit), to awireless device, one or more messages comprising ansCellDeactivationTimer timer. The wireless device may deactivate anSCell, for example, after or in response to an expiry of thesCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell activation/deactivation MAC CE activating anSCell. The wireless device may perform operations (e.g., after or inresponse to the activating the SCell) that may comprise: SRStransmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for theSCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring forthe SCell on the PCell; and/or PUCCH transmissions on the SCell.

The wireless device may start and/or restart a timer (e.g., ansCellDeactivationTimer timer) associated with the SCell, for example,after or in response to activating the SCell. The wireless device maystart the timer (e.g., sCellDeactivationTimer timer) in the slot, forexample, if the SCell activation/deactivation MAC CE has been received.The wireless device may initialize and/or re-initialize one or moresuspended configured uplink grants of a configured grant Type 1associated with the SCell according to a stored configuration, forexample, after or in response to activating the SCell. The wirelessdevice may trigger a PHR, for example, after or in response toactivating the SCell.

The wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell activation/deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a timer (e.g., ansCellDeactivationTimer timer) associated with an activated SCellexpires. The wireless device may stop the timer (e.g.,sCellDeactivationTimer timer) associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may clear one or more configured downlink assignmentsand/or one or more configured uplink grant Type 2 associated with theactivated SCell, for example, after or in response to the deactivatingthe activated SCell. The wireless device may suspend one or moreconfigured uplink grant Type 1 associated with the activated SCell,and/or flush HARQ buffers associated with the activated SCell, forexample, after or in response to deactivating the activated SCell.

A wireless device may refrain from performing certain operations, forexample, if an SCell is deactivated. The wireless device may refrainfrom performing one or more of the following operations if an SCell isdeactivated: transmitting SRS on the SCell; reporting CQI, PMI, RI,and/or CRI for the SCell on a PCell; transmitting on UL-SCH on theSCell; transmitting on a RACH on the SCell; monitoring at least onefirst PDCCH on the SCell; monitoring at least one second PDCCH for theSCell on the PCell; and/or transmitting a PUCCH on the SCell.

A wireless device may restart a timer (e.g., an sCellDeactivationTimertimer) associated with the activated SCell, for example, if at least onefirst PDCCH on an activated SCell indicates an uplink grant or adownlink assignment. A wireless device may restart a timer (e.g., ansCellDeactivationTimer timer) associated with the activated SCell, forexample, if at least one second PDCCH on a serving cell (e.g. a PCell oran SCell configured with PUCCH, such as a PUCCH SCell) scheduling theactivated SCell indicates an uplink grant and/or a downlink assignmentfor the activated SCell. A wireless device may abort the ongoing randomaccess procedure on the SCell, for example, if an SCell is deactivatedand/or if there is an ongoing random access procedure on the SCell.

FIG. 19A shows an example of an SCell activation/deactivation MAC CEthat may comprise one octet. A first MAC PDU subheader comprising afirst LCID may identify the SCell activation/deactivation MAC CE of oneoctet. An SCell activation/deactivation MAC CE of one octet may have afixed size. The SCell activation/deactivation MAC CE of one octet maycomprise a single octet. The single octet may comprise a first number ofC-fields (e.g., seven) and a second number of R-fields (e.g., one).

FIG. 19B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID may identifythe SCell Activation/Deactivation MAC CE of four octets. An SCellactivation/deactivation MAC CE of four octets may have a fixed size. TheSCell activation/deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g., 1). A Ci field may indicatean activation/deactivation status of an SCell with an SCell index i, forexample, if an SCell with SCell index i is configured. An SCell with anSCell index i may be activated, for example, if the Ci field is set toone. An SCell with an SCell index i may be deactivated, for example, ifthe Ci field is set to zero. The wireless device may ignore the Cifield, for example, if there is no SCell configured with SCell index i.An R field may indicate a reserved bit. The R field may be set to zero.

A base station and/or a wireless device may have multiple antennas, forexample, to support a transmission with high data rate (such as in an NRsystem). A wireless device may perform one or more beam managementprocedures, as shown in FIG. 9B, for example, if configured withmultiple antennas.

A wireless device may perform a downlink beam management based on one ormore CSI-RSs and/or one or more SS blocks. In a beam managementprocedure, a wireless device may measure a channel quality of a beampair link. The beam pair link may comprise a transmitting beam from abase station and a receiving beam at the wireless device. A wirelessdevice may measure the multiple beam pair links between the base stationand the wireless device, for example, if the wireless device isconfigured with multiple beams associated with multiple CSI-RSs and/orSS blocks.

A wireless device may send (e.g., transmit) one or more beam managementreports to a base station. The wireless device may indicate one or morebeam pair quality parameters, for example, in a beam management report.The one or more beam pair quality parameters may comprise at least oneor more beam identifications; RSRP; and/or PMI, CQI, and/or RI of atleast a subset of configured multiple beams.

A base station and/or a wireless device may perform a downlink beammanagement procedure on one or multiple Transmission and Receiving Point(TRPs), such as shown in FIG. 9B. Based on a wireless device's beammanagement report, a base station may send (e.g., transmit), to thewireless device, a signal indicating that a new beam pair link is aserving beam. The base station may transmit PDCCH and/or PDSCH to thewireless device using the serving beam.

A wireless device and/or a base station may trigger a beam failurerecovery mechanism. A wireless device may trigger a beam failurerecovery (BFR) procedure, for example, if at least a beam failureoccurs. A beam failure may occur if a quality of beam pair link(s) of atleast one PDCCH falls below a threshold. The threshold comprise be anRSRP value (e.g., −140 dbm, −110 dbm, or any other value) and/or a SINRvalue (e.g., −3 dB, −1 dB, or any other value), which may be configuredin a RRC message.

FIG. 20A shows an example of a first beam failure event. A base station2002 may send (e.g., transmit) a PDCCH from a transmission (Tx) beam toa receiving (Rx) beam of a wireless device 2001 from a TRP. The basestation 2002 and the wireless device 2001 may start a beam failurerecovery procedure on the TRP, for example, if the PDCCH on the beampair link (e.g., between the Tx beam of the base station 2002 and the Rxbeam of the wireless device 2001) have a lower-than-threshold RSRPand/or SINR value due to the beam pair link being blocked (e.g., by amoving vehicle 2003, a building, or any other obstruction).

FIG. 20B shows an example of a second beam failure event. A base stationmay send (e.g., transmit) a PDCCH from a beam to a wireless device 2011from a first TRP 2014. The base station and the wireless device 2011 maystart a beam failure recovery procedure on a new beam on a second TRP2012, for example, if the PDCCH on the beam is blocked (e.g., by amoving vehicle 2013, building, or any other obstruction).

A wireless device may measure a quality of beam pair links using one ormore RSs. The one or more RSs may comprise one or more SS blocks and/orone or more CSI-RS resources. A CSI-RS resource may be determined by aCSI-RS resource index (CRI). A quality of beam pair links may beindicated by, for example, an RSRP value, a reference signal receivedquality (e.g., RSRQ) value, and/or a CSI (e.g., SINR) value measured onRS resources. A base station may indicate whether an RS resource, usedfor measuring beam pair link quality, is QCLed (Quasi-Co-Located) withDM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH may beQCLed, for example, if the channel characteristics from a transmissionon an RS to a wireless device, and that from a transmission on a PDCCHto the wireless device, are similar or same under a configuredcriterion. The RS resource and the DM-RSs of the PDCCH may be QCLed, forexample, if Doppler shift and/or Doppler shift of the channel from atransmission on an RS to a wireless device, and that from a transmissionon a PDCCH to the wireless device, are the same.

A wireless device may monitor a PDCCH on M beams (e.g. 2, 4, 8) pairlinks simultaneously, where M≥1 and the value of M may depend at leaston capability of the wireless device. Monitoring a PDCCH may comprisedetecting DCI via the PDCCH transmitted on common search spaces and/orwireless device specific search spaces. Monitoring multiple beam pairlinks may increase robustness against beam pair link blocking. A basestation may send (e.g., transmit) one or more messages comprisingparameters indicating a wireless device to monitor PDCCH on differentbeam pair link(s) in different OFDM symbols.

A base station may send (e.g., transmit) one or more RRC messages and/orMAC CEs comprising parameters indicating Rx beam setting of a wirelessdevice for monitoring PDCCH on multiple beam pair links. A base stationmay send (e.g., transmit) an indication of a spatial QCL between DL RSantenna port(s) and DL RS antenna port(s) for demodulation of DL controlchannel. The indication may comprise a parameter in a MAC CE, an RRCmessage, DCI, and/or any combinations of these signaling.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of DL data channel, for example, forreception of data packet on a PDSCH. A base station may send (e.g.,transmit) DCI comprising parameters indicating the RS antenna port(s)are QCLed with DM-RS antenna port(s).

A wireless device may measure a beam pair link quality based on CSI-RSsQCLed with DM-RS for PDCCH, for example, if a base station sends (e.g.,transmits) a signal indicating QCL parameters between CSI-RS and DM-RSfor PDCCH. The wireless device may start a BFR procedure, for example,if multiple contiguous beam failures occur.

A wireless device may send (e.g., transmit) a BFR signal on an uplinkphysical channel to a base station, for example, if starting a BFRprocedure. The base station may send (e.g., transmit) DCI via a PDCCH ina CORESET, for example, after or in response to receiving the BFR signalon the uplink physical channel. The wireless may determine that the BFRprocedure is successfully completed, for example, after or in responseto receiving the DCI via the PDCCH in the CORESET.

A base station may send (e.g., transmit) one or more messages comprisingconfiguration parameters of an uplink physical channel, or signal, fortransmitting a beam failure recovery request. The uplink physicalchannel or signal may be based on one of: a contention-free PRACH(BFR-PRACH), which may be a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., BFR-PUCCH); and/or acontention-based PRACH resource (e.g., CF-PRACH). Combinations of thesecandidate signals and/or channels may be configured by the base station.A wireless device may autonomously select a first resource fortransmitting the BFR signal, for example, if the wireless device isconfigured with multiple resources for a BFR signal. The wireless devicemay select a BFR-PRACH resource for transmitting a BFR signal, forexample, if the wireless device is configured with the BFR-PRACHresource, a BFR-PUCCH resource, and/or a CF-PRACH resource. The basestation may send (e.g., transmit) a message to the wireless deviceindicating a resource for transmitting the BFR signal, for example, ifthe wireless device is configured with a BFR-PRACH resource, a BFR-PUCCHresource, and/or a CF-PRACH resource.

A base station may send (e.g., transmit) a response to a wirelessdevice, for example, after receiving one or more BFR signals. Theresponse may comprise the CRI associated with the candidate beam thatthe wireless device may indicate in the one or multiple BFR signals.

A base station and/or a wireless device may perform one or more beammanagement procedures, for example, if the base station and/or thewireless device are configured with multiple beams (e.g., in system suchas in an NR system). The wireless device may perform a BFR procedure(e.g., send one or more BFR signals), for example, if one or more beampair links between the base station and the wireless device fail.

A wireless device may receive one or more RRC messages that comprise BFRparameters. The one or more RRC messages may comprise one or more of anRRC connection reconfiguration message, an RRC connectionreestablishment message, and/or an RRC connection setup message. Thewireless device may detect at least one beam failure according to atleast one of BFR parameters and trigger a BFR procedure. The wirelessdevice may start a first timer, if configured, in response to detectingthe at least one beam failure. The wireless device may select a beam(e.g., a selected beam) in response to detecting the at least one beamfailure. The selected beam may be a beam with good channel quality(e.g., determined based on RSRP, SINR, or BLER, etc.) from a set ofcandidate beams. The set of candidate beams may be identified by a setof reference signals (e.g., SSBs, or CSI-RSs). The wireless device maytransmit at least a first BFR signal to a base station in response toselecting the selected beam. The at least first BFR signal may beassociated with the selected beam. The at least first BFR signal may be,for example, a preamble transmitted on a PRACH resource, or a beamfailure request (e.g., which may be similar to an SR) signal transmittedon a PUCCH resource, or a beam indication transmitted on a PUCCH/PUSCHresource. The wireless device may transmit the at least first BFR signalwith a transmission beam corresponding to a receiving beam associatedwith the selected beam. The wireless device, may, for example, determinetransmission beam by using the RF and/or digital beamforming parameterscorresponding to the receiving beam. The wireless device may start aresponse window in response to transmitting the at least first BFRsignal. The response window may be tracked using, for example, a timerwith a value configured by the base station. The wireless device maymonitor a PDCCH in a first CORESET while the response window is running.The first CORESET may be associated with the BFR procedure. The wirelessdevice may monitor the PDCCH in the first CORESET in condition oftransmitting the at least first BFR signal. The wireless device mayreceive a first DCI via the PDCCH in the first CORESET while theresponse window is running. The wireless device may consider the BFRprocedure successfully completed if the wireless device receives thefirst DCI via the PDCCH in the first CORESET before the response windowexpires. The wireless device may stop the first timer, if configured, ifthe BFR procedure is successfully completed.

FIG. 21 shows an example of a BFR procedure. In some communicationsystems, a wireless device may stop a BWP inactivity timer if a randomaccess procedure is initiated, and/or the wireless device may restartthe BWP inactivity timer if the random access procedure is successfullycompleted (e.g., based on or in response to receiving DCI addressed to aC-RNTI of the wireless device). At step 2100, a wireless device mayreceive one or more RRC messages comprising BFR parameters. At step2102, the wireless device may detect at least one beam failure accordingto at least one BFR parameter. The wireless device may start a firsttimer, if configured, based on detecting the at least one beam failure.At step 2104, the wireless device may select a beam (e.g., a selectedbeam) based on detecting the at least one beam failure. The selectedbeam may be a beam with good channel quality (e.g., based on RSRP, SINR,and/or BLER) that may be selected from a set of candidate beams. Thecandidate beams may be indicated by a set of reference signals (e.g.,SSBs, or CSI-RSs). At step 2106, the wireless device may send (e.g.,transmit) at least a first BFR signal to a base station, for example,based on selecting the beam (e.g., selected beam). The at least firstBFR signal may be associated with the selected beam. The wireless devicemay send (e.g., transmit) the at least first BFR signal with atransmission beam corresponding to a receiving beam associated with theselected beam. The at least first BFR signal may be a preamble sent(e.g., transmitted) via a PRACH resource, an SR signal sent (e.g.,transmitted) via a PUCCH resource, a beam failure recovery signal sent(e.g., transmitted) via a PUCCH resource, a beam indication (e.g., beamfailure recovery medium access control control element (BFR MAC CE))transmitted on a PUCCH/PUSCH resource, and/or a beam report sent (e.g.,transmitted) via a PUCCH and/or PUSCH resource. At step 2108, thewireless device may start a response window, for example, based onsending (e.g., transmitting) the at least first BFR signal. The responsewindow may be associated with a timer with a value configured by thebase station. The wireless device may monitor a PDCCH in a first CORESET(e.g., UE specific or dedicated to the wireless device or wirelessdevice specific), for example, if the response window is running. Thefirst CORESET may be configured by the BFR parameters (e.g., RRC). Thefirst CORESET may be associated with the BFR procedure. The wirelessdevice may monitor the PDCCH in the first CORESET in condition oftransmitting the at least first BFR signal.

At step 2110, the wireless device may detect (e.g., receive) a first DCIvia the PDCCH in the first CORESET, for example, if the response windowis running. At step 2112, the wireless device may determine that the BFRprocedure has successfully completed, for example, if the wirelessdevice receives the first DCI via the PDCCH in the first CORESET beforethe response window expires. The wireless device may stop the firsttimer, if configured, based on the BFR procedure successfully beingcompleted. The wireless device may stop the response window, forexample, based on the BFR procedure successfully being completed. If theresponse window expires, and the wireless device does not receive theDCI (e.g., at step 2110), the wireless device may, at step 2114,increment a transmission number. The transmission number may beinitialized to a first number (e.g., 0) before the BFR procedure istriggered. At step 2114, if the transmission number indicates a numberless than the configured maximum transmission number, the wirelessdevice may repeat one or more actions (e.g., at step 2104). The one ormore actions to be repeated may comprise at least one of a BFR signaltransmission, starting the response window, monitoring the PDCCH, and/orincrementing the transmission number, for example, if no responsereceived during the response window is running. At step 2116, if thetransmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device may declarethe BFR procedure is unsuccessfully completed.

A MAC entity of a wireless device may be configured by an RRC message,for example, for a beam failure recovery procedure. The beam failurerecovery procedure may be used for indicating to a serving base stationof a new (e.g., candidate) synchronization signal block (SSB) and/orCSI-RS, for example, if a beam failure is detected. The beam failure maybe detected on one or more serving SSB(s) and/or CSI-RS(s) of theserving base station. The beam failure may be detected by counting abeam failure instance indication from a lower layer of the wirelessdevice (e.g., PHY layer) to the MAC entity.

An RRC message may configure a wireless device with one or moreparameters (e.g., in BeamFailureRecoveryConfig) for a beam failuredetection and recovery procedure. The one or more parameters maycomprise one or more of: beamFailureInstanceMaxCount for a beam failuredetection, beamFailureDetectionTimer for the beam failure detection,beamFailureRecoveryTimer for a beam failure recovery procedure,rsrp-ThresholdSSB, an RSRP threshold for a beam failure recovery,PowerRampingStep for the beam failure recovery,preambleReceivedTargetPower for the beam failure recovery, preambleTxMaxfor the beam failure recovery, and/or ra-ResponseWindow. Thera-ResponseWindow may be a time window to monitor one or more responsesfor the beam failure recovery using a contention-free RA preamble.

FIG. 22 shows an example of beam failure instance (BFI) indication. Awireless device may use at least one wireless device variable for a beamfailure detection. A BFI counter (e.g., BFI_COUNTER) may be one of theat least one wireless device variable. The BFI counter may be a counterfor a beam failure instance indication. The BFI counter may be initiallyset to zero before time T 2200. The wireless device may start or restarta beam failure detection timer (e.g., beamFailureDetectionTimer) at timeT 2200 and increment the BFI counter, for example, based on a MAC entityof a wireless device receiving a beam failure instance indication from alower layer (e.g., PHY) of the wireless device. The wireless device mayincrement the BFI counter, for example, in addition to starting orrestarting the beam failure detection timer (e.g., BFR timer in FIG. 22at time T 2200, 2T 2202, 4T 2206, 5T 2208, 6T 2210, etc.). The wirelessdevice may initiate a random access procedure such as for a beam failurerecovery (e.g., on an SpCell) based on the BFI counter being greaterthan or equal to a value such as beamFailureInstanceMaxCount (e.g., attime T 2200, 2T 2202, 5T 2208 in FIG. 22 ), for example, if an active ULBWP is configured with BeamFailureRecoveryConfig. The wireless devicemay start a beam failure recovery timer (e.g., beamFailureRecoveryTimer,if configured), for example, based on the active UL BWP being configuredwith a beam failure recovery configuration (e.g.,BeamFailureRecoveryConfig). The wireless device may start the beamfailure recovery timer, for example, based on or in response to a BFIcounter (e.g., BFI_COUNTER) being equal to or greater than a value suchas beamFailureInstanceMaxCount. The wireless device may use the one ormore parameters in the beam failure recover configuration (e.g.,powerRampingStep, preambleReceivedTargetPower, and/or preambleTransMax),for example, based on or in response to the initiating the random accessprocedure. The wireless device may set the BFI counter to zero, forexample, based on the beam failure detection timer expiring. Thewireless device may determine that the beam failure recovery procedurehas successfully completed, for example, based on the random accessprocedure being successfully completed. The random access procedure maybe a contention-free random access procedure.

A wireless device may initiate a random access procedure (e.g., on anSpCell) for a beam failure recovery, for example, based on or inresponse to a BFI counter (e.g., BFI_COUNTER) being greater than orequal to a value such as beamFailureInstanceMaxCount and if the activeUL BWP is not configured with BeamFailureRecoveryConfig. The randomaccess procedure may be a contention-based random access procedure.

A wireless device may initiate a random access procedure at time 6T2210, for example, if a first number (e.g., 3) is reached. The wirelessdevice may set the BFI counter to zero (e.g., in FIG. 22 , between time3T 2204 and 4T 2206), for example, based on the beam failure detectiontimer (e.g., beamFailureDetectionTimer) expiring. The wireless devicemay set the BFI_COUNTER to zero, for example, based on thebeamFailureDetectionTimer, the BFI_COUNTER, or any of the referencesignals used for beam failure detection (e.g., RadioLinkMonitoring RS)being reconfigured by higher layers (e.g., RRC). The wireless device maydetermine that the beam failure recovery procedure has successfullycompleted, for example, based on the random access procedure (e.g., acontention-free random access or a contention-based random access) beingsuccessfully completed. The wireless device may stop the beam failurerecovery timer (if configured), for example, based on the random accessprocedure (e.g., a contention-free random access) is successfullycompleted. The wireless device may reset the BFI_COUNTER to zero, forexample, based on the random access procedure (e.g., contention-freerandom access) is successfully completed.

A MAC entity may start ra-ResponseWindow at a first PDCCH occasion fromthe end of the transmitting the contention-free random access preamble,for example, if a MAC entity of a wireless device sends (e.g.,transmits) a contention-free random access preamble for a BFR procedure.The ra-ResponseWindow may be configured in BeamFailureRecoveryConfig.The wireless device may monitor at least one PDCCH (e.g., of an SpCell)for a response to the beam failure recovery request, for example, if thera-ResponseWindow is running. The beam failure recovery request may beidentified by a C-RNTI. The wireless device may determine that a randomaccess procedure has successfully completed, for example, if a MACentity of a wireless device receives, from a lower layer of the wirelessdevice, a notification of a reception of at least one PDCCHtransmission, and if the at least one PDCCH transmission is addressed toa C-RNTI, and/or if a contention-free random access preamble for a beamfailure recovery request is transmitted by the MAC entity.

A wireless device may initiate a contention-based random access preamblefor a beam failure recovery request. A MAC entity of the wireless devicemay start ra-ContentionResolutionTimer, for example, if the wirelessdevice transmits Msg3. The ra-ContentionResolutionTimer may beconfigured by RRC. Based on the starting thera-ContentionResolutionTimer, the wireless device may monitor at leastone PDCCH if the ra-ContentionResolutionTimer is running. The wirelessdevice may consider the random access procedure successfully completed,for example, if the MAC entity receives, from a lower layer of thewireless device, a notification of a reception of the at least one PDCCHtransmission, if a C-RNTI MAC CE is included in the Msg3, if a randomaccess procedure is initiated for a beam failure recovery, and/or the atleast one PDCCH transmission is addressed to a C-RNTI of the wirelessdevice. The wireless device may stop the ra-ContentionResolutionTimer,for example, based on the random access procedure being successfullycompleted. The wireless device may determine that the beam failurerecovery has successfully completed, for example, if a random accessprocedure of a beam failure recovery is successfully completed.

A wireless device may be configured (e.g., for a serving cell) with afirst set of periodic CSI-RS resource configuration indexes by a higherlayer parameter (e.g., Beam-Failure-Detection-RS-ResourceConfig,failureDetectionResources, etc.). The higher layer parameterBeam-Failure-Detection-RS-ResourceConfig may be configured on a downlinkBWP (of the configured downlink BWPs) of the serving cell. The wirelessdevice may be configured with a second set of CSI-RS resourceconfiguration indexes and/or SS/PBCH block indexes by a higher layerparameter (e.g., Candidate-Beam-RS-List, candidateBeamRSList, etc.). Thehigher layer parameter Candidate-Beam-RS-List may be configured on anuplink BWP (of the configured uplink BWPs) of the serving cell. Thefirst set of CSI-RS resource configuration indexes and/or SS/PBCH blockindexes and/or the second set of CSI-RS resource configuration indexesand/or SS/PBCH block indexes may be used for radio link qualitymeasurements on the serving cell. The wireless device may determine afirst set to include SS/PBCH block indexes and/or periodic CSI-RSresource configuration indexes, for example, if a wireless device is notprovided with higher layer parameterBeam-Failure-Detection-RS-ResourceConfig. The SS/PBCH block indexes andthe periodic CSI-RS resource configuration indexes may comprise the samevalues as one or more RS indexes in one or more RS sets. The one or moreRS indexes in the one or more RS sets may be indicated by one or moreTCI states (e.g., via a higher layer parameter TCI-States). The one ormore TCI states may be used for respective CORESETs for which thewireless device may be configured to monitor a PDCCH. The wirelessdevice may expect the first set to include up to two RS indexes. Thefirst set may include one or more RS indexes with QCL-TypeDconfiguration for the TCI state, for example, if there are two RSindexes in a TCI state. The wireless device may expect a single port RSin the first set.

A first threshold (e.g., Qout,LR) may correspond to a first defaultvalue of a first higher layer parameter (e.g.,RLM-IS-OOS-thresholdConfig, rlmInSyncOutOfSyncThreshold, etc.). A secondthreshold (e.g., Qin,LR) may correspond to a second default value of ahigher layer parameter (e.g., Beam-failure-candidate-beam-threshold,rsrp-ThresholdSSB, etc.). A physical layer in the wireless device maydetermine (or assess) a first radio link quality based on the firstthreshold. The wireless device may determine (or assess) the first radiolink quality based on periodic CSI-RS resource configurations or SS/PBCHblocks. The periodic CSI-RS resource configurations and/or the SS/PBCHblocks may be associated (e.g., quasi co-located) with at least oneDM-RS of a PDCCH that may be monitored by the wireless device. Thewireless device may apply the second threshold to a first L1-RSRPmeasurement that may be obtained from one or more SS/PBCH blocks. Thewireless device may apply the second threshold to a second L1-RSRPmeasurement that may be obtained from one or more periodic CSI-RSresources, for example after scaling a respective CSI-RS reception powerwith a value provided by a higher layer parameter (e.g., Pc_SS,powerControlOffsetSS, etc.).

A wireless device may assess the first radio link quality of a first set(e.g., of resources). A physical layer in the wireless device mayprovide an indication to higher layers (e.g., MAC), for example, if thefirst radio link quality for all corresponding resource configurationsin the first set is less than the first threshold. The physical layermay inform the higher layers (e.g., MAC, RRC), for example, if the firstradio link quality is less than the first threshold with a firstperiodicity. The first periodicity may be determined by the maximum ofthe shortest periodicity of periodic CSI-RS configurations or SS/PBCHblocks in the first set and a time value (e.g., 2 ms or any otherduration). The wireless device may access the periodic CSI-RSconfigurations or the SS/PBCH blocks for the first radio link quality.Based on a request from higher layers (e.g., MAC layer), a wirelessdevice may provide to higher layers the periodic CSI-RS configurationindexes and/or the SS/PBCH block indexes from the second set. Thewireless device may provide, to higher layers, corresponding L1-RSRPmeasurements that may be greater than or equal to the second threshold.

A wireless device may be configured with one CORESET, for example, by ahigher layer parameter (e.g., Beam-failure-Recovery-Response-CORESET)and/or via a link to a search space set. The coreset may be UE specificor dedicated to the wireless device or wireless device specific. Thewireless device may be configured with an associated search space thatmay be provided by a higher layer parameter (e.g., search-space-config,recoverySearchSpaceId, etc.). The search space may be used formonitoring a PDCCH in the control resource set. The wireless device maynot expect to be provided with a second search space set for monitoringPDCCH in the CORESET, for example, if the wireless device is provided bya higher layer parameter (e.g., recoverySearchSpaceId). The CORESET maybe associated with the search space set provided by a higher layerparameter (e.g., recoverySearchSpaceId). The wireless device may receivefrom higher layers (e.g., MAC layer), by a parameter (e.g.,PRACH-ResourceDedicatedBFR), a configuration for a PRACH transmission.For the PRACH transmission in slot n and based on antenna port quasico-location parameters associated with periodic CSI-RS resourceconfiguration or with SS/PBCH block associated with a first RS indexprovided by higher layers, the wireless device may monitor the PDCCH ina search space set (e.g., which may be provided by a higher layerparameter such as recoverySearchSpaceId) for detection of a DCI formatstarting from a slot (e.g., slot n+4) within a window. The window may beconfigured by a higher layer parameter (e.g.,Beam-failure-recovery-request-window, BeamFailureRecoveryConfig, etc.).The DCI format may be CRC scrambled by a C-RNTI or MCS-C-RNTI. The firstRS index may be provided by the higher layers. For a PDCCH monitoringand for a corresponding PDSCH reception, the wireless device may use thesame antenna port quasi-collocation parameters associated with the firstRS index (e.g., as for monitoring the PDCCH) until the wireless devicereceives, by higher layers, an activation for a TCI state or a parameter(e.g., any of parameters TCI-StatesPDCCH-ToAddlist,TCI-StatesPDCCH-ToReleaseList).

A wireless device may monitor downlink and/or control channel resources(e.g., PDCCH) candidates in a search space set. The wireless device maymonitor the downlink and/or control channel resources (e.g., PDCCH)candidates in the search space set, for example, at least until thewireless device receives a MAC CE activation command for a TCI state ora higher layer parameter (e.g., TCI-StatesPDCCH-ToAddlist and/orTCI-StatesPDCCH-ToReleaseList), for example, after the wireless devicedetects the DCI format with CRC scrambled by the C-RNTI or theMCS-C-RNTI in the search space set (e.g., which may be by the higherlayer parameter recoverySearchSpaceId). The wireless device may notinitiate and/or perform a contention free random access procedure for abeam failure recovery, for example, based on or in response to not beingprovided with the higher layer parameter (e.g., recoverySearchSpaceId).A wireless device may initiate and/or perform a contention-based randomaccess procedure for a beam failure recovery, for example, based on orin response to not being provided with the higher layer parameter (e.g.,recoverySearchSpaceId).

A wireless device may be configured for each DL BWP of an SpCell with aset of resource indexes for radio link monitoring by a higher layerparameter (e.g., failureDetectionResources), for example, based on acorresponding set of higher layer parameters (e.g.,RadioLinkMonitoringRS). The wireless device may be provided with, forexample, one or more of: a CSI-RS resource configuration index, a higherlayer parameter csi-RS-Index, a SS/PBCH block index, and/or a higherlayer parameter ssb-Index.

The wireless device may use a first RS provided by a higher layerparameter (e.g., TCI-States) for PDCCH receptions, for example, if thewireless device is not provided a higher layer parameter (e.g.,RadioLinkMonitoringRS) and/or if the wireless device is provided ahigher layer parameter (e.g., TCI-States) for PDCCH receptions thatcomprises only one RS (e.g., the first RS). The wireless device may usea first RS provided by the higher layer parameter (e.g., TCI-States) forPDCCH receptions, for example, if the wireless device is not provided ahigher layer parameter (e.g., RadioLinkMonitoringRS) and/or if thewireless device is provided a higher layer parameter (e.g., TCI-States)for PDCCH receptions that comprises two RSs. The first RS may compriseand/or be associated with QCL-TypeD. The wireless device may use thefirst RS for radio link monitoring based on the first RS comprisingand/or being associated with QCL-TypeD. The two RSs may not compriseand/or be associated with QCL-TypeD simultaneously. The wireless devicemay not use an aperiodic or semi-persistent RS for radio linkmonitoring, for example, if the wireless device is not provided a higherlayer parameter (e.g., RadioLinkMonitoringRS) and/or if the wirelessdevice is provided a higher layer parameter (e.g., TCI-States) for PDCCHreceptions.

A base station may configure a wireless device with uplink (UL)bandwidth parts (BWPs) and downlink (DL) BWPs, for example, to enablebandwidth adaptation (BA) for a PCell. The base station may configurethe wireless device with at least DL BWP(s) (e.g., an SCell may not haveUL BWPS) to enable BA for an SCell, for example, if CA is configured.For the PCell, a first initial BWP may be a first BWP used for initialaccess. For the SCell, a second initial BWP may be a second BWPconfigured for the wireless device to first operate on the SCell if theSCell is activated.

A wireless device may switch a first (e.g., active) DL BWP and a first(e.g., active) UL BWP independently, for example, in paired spectrum(e.g., FDD). A wireless device may switch a second (e.g., active) DL BWPand a second (e.g., active) UL BWP simultaneously, for example, inunpaired spectrum (e.g., TDD). Switching between configured BWPs may bebased on DCI and/or an inactivity timer. An expiry of the inactivitytimer associated with a cell may switch an active BWP to a default BWP,for example, if the inactivity timer is configured for a serving cell.The default BWP may be configured by the network.

One UL BWP for each uplink carrier and one DL BWP may be active at atime in an active serving cell, for example, in FDD systems configuredwith BA. One DL/UL BWP pair may be active at a time in an active servingcell, for example, in TDD systems. Operating on the one UL BWP and theone DL BWP (and/or the one DL/UL pair) may enable a wireless device touse a reasonable amount of power (e.g., reasonable battery consumption).BWPs other than the one UL BWP and the one DL BWP that the wirelessdevice may be configured with may be deactivated. The wireless devicemay refrain from monitoring a PDCCH, and/or may refrain fromtransmitting via a PUCCH, PRACH and/or UL-SCH, for example, ondeactivated BWPs.

A serving cell may be configured with a first number (e.g., four) ofBWPs. A wireless device and/or a base station may have one active BWP atany point in time, for example, for an activated serving cell (e.g.,PCell, SCell). A BWP switching for a serving cell may be used toactivate an inactive BWP and/or deactivate an active BWP. The BWPswitching may be controlled by a PDCCH indicating a downlink assignmentor an uplink grant. The BWP switching may be controlled by an inactivitytimer (e.g., bwpInactivityTimer). The BWP switching may be controlled byan RRC signaling. The BWP switching may be controlled by a MAC entity,for example, based on initiating a random access procedure. A DL BWP(e.g., indicated by first ActiveDownlinkBWP-ID which may be included inRRC signaling) and/or an UL BWP (e.g., indicated byfirstActiveDuplinkBWP-ID which may be included in RRC signaling) may beinitially active without receiving a PDCCH indicating a downlinkassignment or an uplink grant, for example, based on an addition of anSpCell or an activation of an SCell. The active BWP for a serving cellmay be indicated by an RRC message and/or a PDCCH message (e.g., PDCCHorder). A DL BWP may be paired with an UL BWP, and/or BWP switching maybe common for both UL and DL, for example, for unpaired spectrum (e.g.,TDD).

A MAC entity, for an activated serving cell (e.g., PCell, SCell), may beconfigured with one or more BWPs and/or may be configured based on theBWP being activated. The MAC entity may perform at least one of:transmitting via an UL-SCH using the one or more BWPs; transmitting viaa RACH using the one or more BWPs based on PRACH occasions beingconfigured; monitoring a PDCCH using the one or more BWPs; transmittingan SRS using the one or more BWPs based on SRS being configured; sending(e.g., transmitting) via a PUCCH using the one or more BWPs based onPUCCH being configured; reporting CSI for one or more BWPs; receivingvia a DL-SCH using the one or more BWPs; initializing or reinitializingany suspended configured uplink grants of configured grant Type 1 usingthe one or more BWPs (e.g., based on a stored configuration, if any);and/or to start in a symbol (e.g., based on a procedure).

A wireless device (e.g., a MAC entity of a wireless device), for anactivated serving cell (e.g., PCell, SCell) configured with one or moreBWPs and/or based on the BWP being deactivated, may not transmit via aUL-SCH using the one or more BWPs; may not transmit via a RACH using theone or more BWPs; may not monitor a PDCCH using the one or more BWPs;may not report CSI for the one or more BWPs; may not transmit via aPUCCH using the one or more BWPs; may not transmit an SRS using the oneor more BWPs, may not receive via a DL-SCH using the one or more BWPs;may clear any configured downlink assignment and configured uplink grantof configured grant Type 2 using the one or more BWPs; and/or maysuspend any configured uplink grant of configured Type 1 using the oneor more BWPs (e.g., inactive BWPs).

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedure(e.g., contention-based random access, contention-free random access) ona serving cell, for example, based on PRACH occasions being configuredfor an active UL BWP, of the serving cell, with an uplink BWP ID; theserving cell being an SpCell; and/or a downlink BWP ID of an active DLBWP of the serving cell not being the same as the uplink BWP ID. Thebase station and/or the wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may switch from the active DL BWP to aDL BWP with a second downlink BWP ID same as the uplink BWP ID, forexample, based on the prior initiation. The base station and/or thewireless device (e.g., a MAC entity of a base station and/or a wirelessdevice) may perform the random access procedure on the DL BWP of theserving cell (e.g., SpCell) and the active UL BWP of the serving cell,for example, based on or in response to the switching.

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedure(e.g., contention-based random access, contention-free random access) ona serving cell (e.g., SCell), for example, based on PRACH occasionsbeing configured for an active UL BWP of the serving cell; and/or theserving cell not being an SpCell. The base station and/or the wirelessdevice (e.g., a MAC entity of a base station and/or a wireless device)may perform the random access procedure on an active DL BWP of an SpCelland an active UL BWP of the serving cell, for example, based on theinitiation.

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedureon a serving cell, for example, based on PRACH resources not beingconfigured for an active UL BWP of the serving cell. The MAC entity mayswitch the active UL BWP to an uplink BWP (initial uplink BWP), forexample, based on the initiation. The uplink BWP may be indicated by RRCsignaling (e.g., initialULBWP). The base station and/or the wirelessdevice (e.g., a MAC entity of a base station and/or a wireless device)may switch an active DL BWP to a downlink BWP (e.g., initial downlinkBWP), for example, based on the serving cell being an SpCell. Thedownlink BWP may be indicated by RRC signaling (e.g., initialDLBWP). Thebase station and/or the wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may perform the random accessprocedure on the uplink BWP and the downlink BWP, for example, based onor in response to the switching.

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedureon a serving cell, for example, based on PRACH resources not beingconfigured for an active UL BWP of the serving cell (e.g., SCell). Thebase station and/or the wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may switch the active UL BWP to anuplink BWP (initial uplink BWP), for example, based on the initiation.The uplink BWP may be indicated by RRC signaling (e.g., initialULBWP).The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may perform the random accessprocedure on the uplink BWP and an active downlink BWP of an SpCell, forexample, based on the serving cell is not an SpCell.

A wireless device may perform BWP switching to a BWP indicated by aPDCCH, for example, if a base station and/or a wireless device (e.g., aMAC entity of a base station and/or a wireless device) receives a PDCCH(e.g., a PDCCH order) for a BWP switching for a serving cell, forexample, if a random access procedure associated with this serving cellis not ongoing. A wireless device may determine whether to switch a BWPor ignore the PDCCH for the BWP switching, for example, if a basestation and/or a wireless device (e.g., a MAC entity of a base stationand/or a wireless device) received a PDCCH for a BWP switching for aserving cell while a random access procedure is ongoing in the MACentity. The wireless device may perform the BWP switching to a new BWPindicated by the PDCCH. The base station and/or the wireless device(e.g., a MAC entity of a base station and/or a wireless device) may stopthe ongoing random access procedure and initiate a second random accessprocedure after or in response to switching to the new BWP, for example,if the MAC entity decides to perform BWP switching to the new BWP (e.g.,which may be indicated by the PDCCH), for example, based on or inresponse to receiving a PDCCH (e.g., other than successful contentionresolution) or an RRC configuration. The base station and/or thewireless device (e.g., a MAC entity of a base station and/or a wirelessdevice) may continue with the ongoing random access procedure on theserving cell, for example if the MAC decides to ignore the PDCCH for theBWP switching.

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may start or restart a BWPinactivity timer associated with the active DL BWP for a variety ofreasons. The MAC entity may start or restart a BWP inactivity timer(e.g., BWP-InactivityTimer) associated with the active DL BWP for anactivated serving cell configured with the BWP inactivity timer, forexample, if one or more of the following occur: if a Default-DL-BWP isconfigured (e.g., via RRC signaling including defaultDownlinkBWPparameter) and an active DL BWP is not a BWP indicated by theDefault-DL-BWP; if the Default-DL-BWP is not configured and the activeDL BWP is not the initial DL BWP (e.g., via RRC signaling includinginitialDownlinkBWPparameter); and/or if one or more of the followingoccur: if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlinkassignment or uplink grant is received on or for the active BWP, and/orif there is not an ongoing random access procedure associated with theactivated serving cell.

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may start or restart the BWPinactivity timer (e.g., BWP-InactivityTimer) associated with the activeDL BWP, for example, if one or more of the following occur: if aBWP-InactivityTimer is configured for an activated serving cell, if aDefault-DL-BWP is configured and an active DL BWP is not a BWP indicatedby the Default-DL-BWP, and/or if the Default-DL-BWP is not configuredand an active DL BWP is not the initial DL BWP; and/or if one or more ofthe following occur: if a MAC-PDU is transmitted in a configured uplinkgrant or received in a configured downlink assignment, and/or if thereis not an ongoing random access procedure associated with the activatedserving cell.

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may start or restart the BWPinactivity timer (e.g., BWP-InactivityTimer) associated with the activeDL BWP, for example, if one or more of the following occur: if aBWP-InactivityTimer is configured for an activated serving cell, if aDefault-DL-BWP is configured and an active DL BWP is not a BWP indicatedby the Default-DL-BWP, and/or if the Default-DL-BWP is not configuredand the active DL BWP is not the initial DL BWP; and/or if one or moreof the following occur: if a PDCCH addressed to C-RNTI or CS-RNTIindicating downlink assignment or uplink grant is received on or for theactive BWP, if a MAC-PDU is transmitted in a configured uplink grant orreceived in a configured downlink assignment, and/or if an ongoingrandom access procedure associated with the activated Serving Cell issuccessfully completed in response to receiving a PDCCH addressed to aC-RNTI.

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may start or restart the BWPinactivity timer (e.g., BWP-InactivityTimer) associated with the activeDL BWP based on switching the active BWP. For example, the MAC entitymay start or restart the BWP-InactivityTimer associated with the activeDL BWP if a PDCCH for BWP switching is received and the wireless deviceswitches an active DL BWP to the DL BWP, and/or if one or more of thefollowing occur: if a default downlink BWP is configured and the DL BWPis not the default downlink BWP, and/or if a default downlink BWP is notconfigured and the DL BWP is not the initial downlink BWP.

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may stop the BWP inactivity timer(e.g., BWP-InactivityTimer) associated with an active DL BWP of theactivated serving cell, for example, if one or more of the followingoccur: if BWP-InactivityTimer is configured for an activated servingcell, if the Default-DL-BWP is configured and the active DL BWP is notthe BWP indicated by the Default-DL-BWP, and/or if the Default-DL-BWP isnot configured and the active DL BWP is not the initial BWP; and/or if arandom access procedure is initiated on the activated serving cell. TheMAC entity may stop a second BWP inactivity timer (e.g.,BWP-InactivityTimer) associated with a second active DL BWP of anSpCell, for example, if the activated Serving Cell is an SCell (otherthan a PSCell).

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may perform BWP switching to aBWP indicated by the Default-DL-BWP, for example, if one or more of thefollowing occur: if a BWP inactivity timer (e.g., BWP-InactivityTimer)is configured for an activated serving cell, if the Default-DL-BWP isconfigured and the active DL BWP is not the BWP indicated by theDefault-DL-BWP, if the Default-DL-BWP is not configured and the activeDL BWP is not the initial BWP, if BWP-InactivityTimer associated withthe active DL BWP expires, and/or if the Default-DL-BWP is configured.The MAC entity may perform BWP switching to the initial DL BWP, forexample, if the MAC entity may refrain from performing BWP switching toa BWP indicated by the Default-DL-BWP.

A wireless device may be configured for operation in BWPs of a servingcell. The wireless device may be configured by higher layers for theserving cell for a set of (e.g., four) bandwidth parts (BWPs) forreceptions by the wireless device (e.g., DL BWP set) in a DL bandwidthby a parameter (e.g., DL-BWP). The wireless device may be configuredwith a set of (e.g., four) BWPs for transmissions by the wireless device(e.g., UL BWP set) in an UL bandwidth by a parameter (e.g., UL-BWP). Awireless device may not be provided higher layer parameterinitialDownlinkBWP. An initial active DL BWP may be determined based onthe wireless device not being provided the higher layer parameterinitialDownlinkBWP, for example, by: a location and number of contiguousPRBs; a subcarrier spacing; and/or a cyclic prefix (e.g., for PDCCHreception via the control resource set for a Type0-PDCCH common searchspace). The contiguous PRBs may start from a PRB with a lowest index andmay end at a PRB with a highest index, for example, for the PRBs of acontrol resource set for Type0-PDCCH common search space. A wirelessdevice may be provided higher layer parameter initialDownlinkBWP. Aninitial active DL BWP may be a BWP indicated by the higher layerparameter initialDownlinkBWP based on the wireless device being providedthe higher layer parameter initialDownlinkBWP. A wireless device may beprovided (e.g., by a higher layer) a parameter (e.g., initial-UL-BWP)for an initial active UL BWP for a random access procedure, for example,for operation on a primary cell or on a secondary cell. The wirelessdevice may be provided with an initial active UL BWP (e.g., by a higherlayer) parameter (e.g., Active-BWP-DL-Pcell, initialUplinkBWP, etc.) forfirst active DL BWP for receptions, for example, if a wireless devicehas a dedicated BWP configuration. The wireless device may be providedwith an initial uplink BWP on a supplementary uplink carrier by a secondhigher layer parameter (e.g., initialUplinkBWP in a supplementaryuplink), for example, if the wireless device is configured with asupplementary uplink carrier. The wireless device may be provided (e.g.,by a higher layer) a parameter (e.g., Active-BWP-UL-Pcell,firstActiveDownlinkBWP-Id, etc.) for a first active UL BWP fortransmissions on a primary cell, for example, if a wireless device has adedicated BWP configuration. The higher layer parameter may indicate afirst active DL BWP for receptions. The wireless device may be providedby a second higher layer parameter (e.g., firstActiveUplinkBWP-Id), forexample, if the wireless device has a dedicated BWP configuration. Thehigher layer parameter may indicate a first active UL BWP fortransmissions on the primary cell.

A wireless device may be provided with at least one of the followingparameters for a serving cell, for example, for a DL BWP in a first setof DL BWPs or an UL BWP in a second set of UL BWPs: a subcarrier spacingby higher layer parameter subcarrierSpacing or UL-BWP-mu; a cyclicprefix by higher layer parameter cyclicPrefix; an index in the first setof DL BWPs or in the second set of UL BWPs by respective higher layerparameters bwp-Id (e.g., DL-BWP-ID, UL-BWP-ID); a third set ofBWP-common and a fourth set of BWP-dedicated parameters by a higherlayer parameter bwp-Common and a higher layer parameter bwp-Dedicated,respectively.

A DL BWP from a first set of configured DL BWPs (e.g., with a DL BWPindex provided by higher layer parameter such as bwp-ID) may be pairedand/or linked with an UL BWP from a second set of configured UL BWPs(e.g., with an UL BWP index provided by higher layer parameter such asbwp-ID). A DL BWP from a first set of configured DL BWPs may be pairedwith an UL BWP from a first set of configured UL BWPs, for example, ifthe DL BWP index and the UL BWP index are equal and/or the same (e.g.,for unpaired spectrum operation). A wireless device may not expect toreceive a configuration where the center frequency for a DL BWP isdifferent from the center frequency for an UL BWP, for example, if theDL-BWP-index of the DL BWP is equal to and/or the same as theUL-BWP-index of the UL BWP (e.g., for unpaired spectrum operation).

A wireless device may be configured with CORESETs for every type ofcommon search space and/or for wireless device-specific search space,for example, for a DL BWP in a first set of DL BWPs on a primary cell.The wireless device may not expect to be configured without a commonsearch space on the PCell, or on the PSCell, of the MCG in the DL BWP(e.g., active DL BWP). The wireless device may be configured withCORESETs for PUCCH transmissions, for example, for an UL BWP in a secondset of UL BWPs of the PCell or of a PUCCH-SCell. A wireless device mayreceive a PDCCH message and/or a PDSCH message in a DL BWP, for example,according to a configured subcarrier spacing and/or a CP length for theDL BWP. A wireless device may send (e.g., transmit) via a PUCCH and/orvia a PUSCH in an UL BWP, for example, according to a configuredsubcarrier spacing and CP length for the UL BWP.

A BWP indicator field value may indicate an active DL BWP, from thefirst set of configured DL BWPs, for DL receptions, for example, if theBWP indicator field is configured in DCI format 1_1. The BWP indicatorfield value may indicate an active UL BWP, from the second set ofconfigured UL BWPs, for UL transmissions.

The wireless device may set the active UL BWP to the UL BWP indicated bythe bandwidth part indicator field in the DCI format 0_1, for example,based on a bandwidth part indicator field being configured in DCI format0_1 and/or the bandwidth part indicator field value indicating an UL BWPdifferent from an active UL BWP. The wireless device may set the activeDL BWP to the DL BWP indicated by the bandwidth part indicator field inthe DCI format 1_1, for example, based on a bandwidth part indicatorfield being configured in DCI format 1_1 and/or the bandwidth partindicator field value indicating a DL BWP different from an active DLBWP.

A wireless device may detect a DCI format 0_1 indicating active UL BWPchange, or a DCI format 1_1 indicating active DL BWP change, forexample, if a corresponding PDCCH is received within first three symbolsof a slot. A wireless device may be provided (e.g., for the primarycell) with a higher layer parameter (e.g., defaultDownlinkBWP-Id). Thehigher layer parameter may indicate a default DL BWP among configured DLBWPs. The default BWP may be the initial active DL BWP, for example, ifa wireless device is not provided a default DL BWP by a higher layerparameter (e.g., defaultDownlinkBWP-Id).

The wireless device procedures on the secondary cell may be same as on aprimary cell. The wireless device procedures on the secondary cell maybe the same as on a primary cell, for example, based on the wirelessdevice being configured for a secondary cell with higher layer parameter(e.g., defaultDownlinkBWP-Id) indicating a default DL BWP among theconfigured DL BWPs and/or the wireless device being configured withhigher layer parameter bwp-inactivitytimer indicating a timer value. Anoperation of the timer value for the secondary cell and the default DLBWP for the secondary cell may be similar to or the same as operationsusing a timer value for the primary cell and a default DL BWP for theprimary cell.

A wireless device may be provided by a higher layer parameter (e.g.,BWP-InactivityTimer). The higher layer parameter may indicate a timerwith a timer value for a serving cell (e.g., primary cell, secondarycell). The wireless device may increment the timer every interval (e.g.,every interval of 1 millisecond for frequency range 1, every 0.5milliseconds for frequency range 2, or any other interval for any otherfrequency range), for example, based on the timer being configured, thetimer running, and/or the wireless device not detecting a DCI format forPDSCH reception on the serving cell for paired spectrum operation. Thewireless device may decrement the timer every interval (e.g., everyinterval of 1 millisecond for frequency range 1, every 0.5 millisecondsfor frequency range 2, or any other interval for any other frequencyrange), for example, based on the timer being configured, the timerrunning, the wireless device not detecting a first DCI format for PDSCHreception and/or the wireless device not detecting a second DCI formatfor PUSCH transmission on the serving cell for unpaired spectrumoperation during the interval.

A wireless device may change an active DL BWP and/or an active UL BWPfor a cell, for example, based on expiration of a BWP inactivity timer.The wireless device may not be required to receive or send (e.g.,transmit) in the cell during a time duration from a beginning of asubframe for frequency range 1, or of half of a subframe for frequencyrange 2, for example, to accommodate a delay in the changing the activeDL BWP or the active UL BWP. The wireless device may not be requiredand/or expected to receive and/or send (e.g., transmit) in the celluntil a beginning of a slot where the wireless device can receive orsend (e.g., transmit), for example, after the BWP inactivity timerexpires.

A wireless device may be configured by a higher layer (e.g., theconfiguration including parameter firstActiveDownlinkBWP-Id and/orparameter firstActiveUplinkBWP-Id). The higher layer parameter (e.g.,firstActiveDownlinkBWP-Id) may indicate a first active DL BWP on aserving cell (e.g., secondary cell). The wireless device may use thefirst active DL BWP on the serving cell as the respective first activeDL BWP. The higher layer parameter (e.g., firstActiveUplinkBWP-Id) mayindicate a first active UL BWP on a serving cell (e.g., secondary cell)or on a supplementary uplink carrier. The wireless device may use thefirst active UL BWP on the serving cell or on the supplementary uplinkcarrier as the respective first active UL BWP.

A wireless device may not expect to send (e.g., transmit) a PUCCH withHARQ-ACK on a PUCCH resource indicated by a DCI format 1_0 or a DCIformat 1_1, for example, based on paired spectrum operation, thewireless device changing its active UL BWP on a primary cell between atime of a detection of the DCI format 1_0 or the DCI format 1_1, and/ora time of a corresponding PUCCH transmission with HARQ-ACK transmissionon the PUCCH. A wireless device may not monitor PDCCH when the wirelessdevice performs RRM measurements over a bandwidth that is not within theactive DL BWP for the wireless device.

A DL BWP index (ID) may be an identifier for a DL BWP. One or moreparameters in an RRC configuration may use the DL BWP-ID to associatethe one or more parameters with the DL BWP. The DL BWP ID of 0 (e.g., DLBWP ID=0) may be associated with the initial DL BWP. An UL BWP index(ID) may be an identifier for an UL BWP. One or more parameters in anRRC configuration may use the UL BWP-ID to associate the one or moreparameters with the UL BWP. The UL BWP ID of 0 (e.g., UL BWP ID=0) maybe associated with the initial UL BWP.

A higher layer parameter (e.g., firstActiveDownlinkBWP-Id) may indicatean ID of a DL BWP to be activated upon performing the reconfiguration,for example, based on a higher layer parameter (e.g.,firstActiveDownlinkBWP-Id) is configured for an SpCell. A higher layerparameter (e.g., firstActiveDownlinkBWP-Id) may indicate an ID of a DLBWP to be used upon MAC-activation of the SCell, for example, based onthe higher layer parameter (e.g., firstActiveDownlinkBWP-Id) beingconfigured for an SCell. A higher layer parameter (e.g.,firstActiveUplinkBWP-Id) may indicate an ID of an UL BWP to be activatedif performing the reconfiguration, for example, based on the higherlayer parameter (e.g., firstActiveUplinkBWP-Id) being configured for anSpCell. A higher layer parameter (e.g., firstActiveUplinkBWP-Id) mayindicate an ID of an UL BWP to be used if MAC-activation of the SCelloccurs, for example, based on a higher layer parameter (e.g.,firstActiveUplinkBWP-Id) being configured for an SCell.

A wireless device, to execute a reconfiguration with sync, may assume(e.g., consider) an uplink BWP indicated in a higher layer parameter(e.g., firstActiveUplinkBWP-Id) to be an active uplink BWP. A wirelessdevice, to execute a reconfiguration with sync, may assume (e.g.,consider) a downlink BWP indicated in a higher layer parameter (e.g.,firstActiveDownlinkBWP-Id) to be an active downlink BWP.

A base station (e.g., a gNB), may configure a wireless device to use oneor more UL BWPs and/or one or more DL BWPs of a cell (e.g., PCell orSCell). A first UL BWP of the one or more UL BWPs may be indicated(e.g., identified) with a first UL BWP index. A first DL BWP of the oneor more DL BWPs may be indicated (e.g., identified) with a first DL BWPindex.

The wireless device may operate on the first DL BWP and/or the first ULBWP. The first DL BWP may be an active downlink BWP and/or the first ULBWP may be an active uplink BWP. The wireless device may switch thefirst DL BWP and the first UL BWP independently, for example, based onusing a paired spectrum (e.g., FDD). The first UL BWP index and thefirst DL BWP index may be different.

The wireless device may switch the first DL BWP and the first UL BWPsimultaneously (e.g., together), for example, based on using an unpairedspectrum (e.g., TDD). The first DL BWP index and the first UL BWP indexmay be the same, for example, in the unpaired spectrum. The first UL BWPand the first DL BWP may be linked (or paired), for example, based on orin response to the switching the first DL BWP and the first UL BWPsimultaneously.

FIG. 23 shows an example of a BWP linkage in a paired spectrum (e.g.,FDD) for a beam failure recovery (BFR) procedure. The base station mayconfigure the wireless device to use or make active an UL BWP (e.g.,UL-BWP-1 2302) linked with a DL BWP (e.g., DL-BWP-1 2304). The wirelessdevice may avoid a delay from BWP switching, for example, if thewireless device determines to perform a BFR procedure and/or a randomaccess procedure.

A wireless device may receive one or more messages comprisingconfiguration parameters of a cell from a base station. Theconfiguration parameters may comprise BWP configuration parameters for aplurality of DL BWPs, for example, comprising DL-BWP-1 2304, DL-BWP-22308 and DL-BWP-3 2312 and for a plurality of UL BWPs comprisingUL-BWP-1 2302, UL-BWP-2 2306 and UL-BWP-3 2310. UL-BWP-1 2302 andDL-BWP-1 2304 may be linked. UL-BWP-2 2306 and DL-BWP-2 2308 may belinked. UL-BWP-3 2310 and DL-BWP-3 2312 may be linked. The BWPconfiguration parameters may include an index of an uplink BWP and anindex of a downlink BWP, which may or may not be linked and may or maynot have different indexes.

The DL-BWP-1 2304, the DL-BWP-2 2308, and the DL-BWP-3 2312 may beindicated by a DL-BWP-1 index, DL-BWP-2 index, and DL-BWP-3 index (e.g.,provided by a higher layer parameter BWP-ID), respectively. The UL-BWP-12302, the UL-BWP-2 2306, and the UL-BWP-3 2310 may be indicated by aUL-BWP-1 index, UL-BWP-2 index, and UL-BWP-3 index (e.g., provided by ahigher layer parameter BWP-ID), respectively. The DL-BWP-1 index and theUL-BWP-1 index may be the same. The DL-BWP-2 index and the UL-BWP-2index may be the same. The DL-BWP-3 index and the UL-BWP-3 index may bethe same. The DL-BWP-1 index and the UL-BWP-1 index being the same maybe an indicator of linked uplink and downlink BWPs.

The configuration parameters may comprise DL-BWP-specific BFRconfiguration parameters (e.g., RadioLinkMonitoringConfig) for at leastone of the plurality of DL BWPs (e.g., DL-BWP-1 2304, DL-BWP-2 2308,DL-BWP-3 2312). The DL-BWP-specific BFR configuration parameters may beBWP specific. The DL-BWP-specific BFR configuration parameters may beBWP dedicated.

First DL-BWP-specific BFR configuration parameters for the DL-BWP-1 2304may comprise one or more first RSs (e.g., RadioLinkMonitoringRS) of theDL-BWP-1 2304 and a first beam failure instance (BFI) counter (e.g.,beamFailureInstanceMaxCount). The wireless device may assess the one ormore first RSs (e.g., SSBs, CSI-RSs) to detect a beam failure of theDL-BWP-1 2304.

Second DL-BWP-specific BFR configuration parameters for the DL-BWP-22308 may comprise one or more second RSs (e.g., RadioLinkMonitoringRS)of the DL-BWP-2 2308 and a second BFI counter (e.g.,beamFailureInstanceMaxCount). The wireless device may assess the one ormore second RSs (e.g., SSBs, CSI-RSs) to detect a beam failure of theDL-BWP-2 2308.

Third DL-BWP-specific BFR configuration parameters for the DL-BWP-3 2312may comprise one or more third RSs (e.g., RadioLinkMonitoringRS) of theDL-BWP-3 2312 and a second BFI counter (e.g.,beamFailureInstanceMaxCount). The wireless device may assess the one ormore third RSs (e.g., SSBs, CSI-RSs) to detect a beam failure of theDL-BWP-3 2312.

The configuration parameters may comprise UL-BWP-specific BFRconfiguration parameters (e.g., BeamFailureRecoveryConfig) for at leastone of the plurality of UL BWPs (e.g., UL-BWP-1 2302, UL-BWP-2 2306,UL-BWP-3 2310). The UL-BWP-specific BFR configuration parameters may beBWP specific. The UL-BWP-specific BFR configuration parameters may beBWP dedicated.

First UL-BWP-specific BFR configuration parameters for the UL-BWP-1 2302may comprise one or more first candidate RSs (e.g., candidateBeamRSList)of the DL-BWP-1 2302 and a first search space set (e.g.,recoverySearchSpaceID) on the DL-BWP-1 2302 in response to the DL-BWP-1index and the UL-BWP-1 index being the same. A second UL-BWP-specificBFR configuration parameters for the UL-BWP-2 2306 may comprise one ormore second candidate RSs (e.g., candidateBeamRSList) of the DL-BWP-22308 and a second search space set on the DL-BWP-2 2308 in response tothe DL-BWP-2 index and the UL-BWP-2 index being the same. A thirdUL-BWP-specific BFR configuration parameters for the UL-BWP-3 2310 maycomprise one or more third candidate RSs (e.g., candidateBeamRSList) ofthe DL-BWP-3 2312 and a second search space set on the DL-BWP-3 2312 inresponse to the DL-BWP-3 index and the UL-BWP-3 index being the same.

The UL-BWP-1 2302 and the DL-BWP-1 2304 may be linked/paired, forexample, in a paired spectrum (e.g., FDD) and in response to theUL-BWP-1 2302 being configured with BFR parameters (e.g., the one ormore first candidate RSs, the first search space set) of the DL-BWP-12304. The DL-BWP-1 index and the UL-BWP-1 index may be the same, forexample, based on the DL-BWP-1 2304 and the UL-BWP-1 2302 being linked.

BWP switching may be common for the DL-BWP-1 and the UL-BWP-1, forexample, based on the DL-BWP-1 and the UL-BWP-1 being linked. Thewireless device may switch the DL-BWP-1 and the UL-BWP-1 simultaneously,in succession, in response to or based on the DL-BWP-1 2304 beinglinked/paired with the UL-BWP-1 2302. In FIG. 23 , the DL-BWP-2 2308 andthe UL-BWP-2 2306 may be linked/paired and the DL-BWP-3 2312 and theUL-BWP-3 2310 may be linked/paired.

One or more linked BWPs may comprise a first pair of the DL-BWP-1 2304and the UL-BWP-1 2302; a second pair of the DL-BWP-2 2308 and theUL-BWP-2 2306; and a third pair of the DL-BWP-3 2312 and the UL-BWP-32310. The wireless device may operate on at least one of the one or morelinked BWPs (e.g., DL-BWP-1 2304 and UL-BWP-1 2302, DL-BWP-2 2308 andUL-BWP-2 2306, or DL-BWP-3 2312 and UL-BWP-3 2310 in FIG. 23 )simultaneously. The DL-BWP-1 2304 and the UL-BWP-1 2302 may be active,for example, at a first time (e.g., slot, subframe, frame) based on theDL-BWP-1 2304 being linked/paired with the UL-BWP-1 2302. The DL-BWP-22308 and the UL-BWP-2 2306 may be active, for example, at a second timebased on the DL-BWP-2 2308 being linked/paired with the UL-BWP-2 2306.The DL-BWP-3 2312 and the UL-BWP-3 2310 may be active, for example, at athird time based on the DL-BWP-3 2312 being linked/paired with theUL-BWP-3 2310.

The DL-BWP-1 2304 and the UL-BWP-2 2306 may not be active, for example,at a first time (e.g., slot) based on the DL-BWP-1 2304 not beinglinked/paired with the UL-BWP-2 2306. The DL-BWP-2 2308 and the UL-BWP-12302 may not be active, for example, at a first time (e.g., slot) basedon the DL-BWP-2 2308 not being linked/paired with the UL-BWP-1 2302.

The wireless device may operate on the DL-BWP-1 2304 and the UL-BWP-12302 simultaneously. The DL-BWP-1 2304 and the UL-BWP-1 2302 may be anactive DL BWP and an active UL BWP, respectively, in response to theoperating. The wireless device may switch the active UL BWP from theUL-BWP-1 2302 to the UL-BWP-2 2306, for example, in response to theDL-BWP-2 2308 being linked to the UL-BWP-2 2306 (e.g., based on thewireless device switching the active DL BWP from the DL-BWP-1 2304 tothe DL-BWP-2 2308). The switching may be triggered, for example, inresponse to receiving a DCI indicating an index for the DL-BWP-2 2308,an expiry of BWP inactivity timer associated with the DL-BWP-1 2304, orreceiving an RRC message indicating the index for DL-BWP-2 2308.

The wireless device may operate on the DL-BWP-1 2304 and the UL-BWP-12302 simultaneously. The DL-BWP-1 2304 and the UL-BWP-1 2302 may be anactive DL BWP and an active UL BWP, respectively, in response to theoperating. The wireless device may switch the active DL BWP from theDL-BWP-1 2304 to the DL-BWP-2 2308, for example, in response to theDL-BWP-2 2308 being linked to the UL-BWP-2 2306 (e.g., based on thewireless device switching the active UL BWP from the UL-BWP-1 2302 tothe UL-BWP-2 2306). The switching may be triggered, for example, inresponse to receiving a DCI indicating an index for UL-BWP-2 2306 orreceiving an RRC message indicating the index for UL-BWP-2 2306.

A wireless device may receive, from a base station, one or more messagescomprising configuration parameters for a plurality of cells. Each cellin the plurality of cells may be a secondary cell. The plurality ofcells may comprise a cell group. The plurality of cells may supportmultiple beam (e.g., multi-beam) operation. The plurality of cells mayshare serving beams. The plurality of cells of the cell group may shareserving beams, for example, at high frequencies. The wireless device mayuse a first serving beam for reception via a downlink control channel(e.g., a PDCCH) in each cell of the plurality of cells, for example,based on the one or more configuration parameters received from the basestation. The wireless device may use a first serving beam for receptionvia a downlink shared channel (e.g., a PDSCH) in each cell of theplurality of cells, for example, based on the one or more configurationparameters received from the base station. The base station may serve afirst cell and a second cell of the cell group, for example, with thefirst serving beam for PDCCH and/or PDSCH channels. The wireless devicemay use the first serving beam for sending (e.g., transmitting) via anuplink control channel (e.g., a PUCCH) in each cell of the plurality ofcells, for example, based on the one or more configuration parametersreceived from the base station. The wireless device may use the firstserving beam for sending (e.g., transmitting) via an uplink sharedchannel (e.g., a PUSCH) in each cell of the plurality of cells, forexample, based on the one or more configuration parameters received fromthe base station. The base station may send (e.g., transmit) a separatereconfiguration message (e.g., RRC, MAC CE, DCI, etc.) for each cell inthe group of secondary cells to change the first serving beam to asecond serving beam (e.g., after a beam failure recovery procedure iscompleted). The wireless device may receive a reconfiguration messagefor each cell in the plurality of cells to change from the first servingbeam to a second serving beam, for example, if the first serving beamfails. Receiving a reconfiguration message for each cell in theplurality of cells may increase a signaling overhead related toswitching from the first serving beam to the second serving beam foreach cell in the plurality of cells (e.g., increased configurationmessage transmission). Receiving a reconfiguration message for each cellin the plurality of cells may increase a delay in establishing operationfor each cell of the plurality of cells. Receiving a reconfigurationmessage for each cell in the plurality of cells may increase aconsumption of a power source (e.g., a battery) of the wireless device.

A PDCCH reconfiguration (e.g., the same PDCCH reconfiguration) may beapplied to all cells in the cell group, for example, based on a PDCCH ofa cell in the cell group being reconfigured (e.g., via RRC, MAC, and/orDCI) with the PDCCH reconfiguration. A PDSCH reconfiguration (e.g., thesame PDSCH reconfiguration) may be applied to all cells in the cellgroup, for example, based on a PDSCH of a cell in the cell group beingreconfigured (e.g., via RRC, MAC, and/or DCI) with the PDSCHreconfiguration. A uplink channel (e.g., PUCCH and/or PUSCH)reconfiguration may be applied to all cells in the cell group, forexample, based on an uplink channel (e.g., PUCCH and/or PUSCH) in thecell group being reconfigured (e.g., via RRC, MAC, and/or DCI) with thereconfiguration. A wireless device may receive, from the base station, afirst reconfiguration message for a first cell in the plurality of cellsto change from the first serving beam to the second serving beam, forexample, if the first serving beam fails. The wireless device may use(e.g., apply) the first reconfiguration message to reconfigure each cellin the plurality of cells (e.g., to reconfigure all cells in a cellgroup). The wireless device may use (e.g., apply) the firstreconfiguration message to change from the first serving beam to thesecond serving beam in each cell in the plurality of cells. The firstreconfiguration message may comprise one or more of: a MAC CE activationcommand, an RRC message, and/or DCI. The first reconfiguration messagemay indicate a TCI state for the first cell. The wireless device may usethe TCI state for each cell in the plurality of cells. The TCI state maycomprise a cell group parameter. The cell group parameter may comprise acell-specific index for each cell in the plurality of cells. Thewireless device may change from the first serving beam to the secondserving beam, for example, based on the TCI state including the cellgroup parameter comprising the cell-specific index for each cell in theplurality of cells.

The wireless device may receive, from the base station, one or more BFRconfiguration parameters for the first cell in the plurality of cells.The one or more BFR configuration parameters may comprise the cell groupparameter comprising the cell-specific index for each cell in theplurality of cells. The wireless device may change from the firstserving beam to the second serving beam based on a reconfigurationmessage for the first cell if the one or more BFR configurationparameters include the cell group parameter comprising the cell-specificindex for each cell in the plurality of cells. The reconfigurationmessage may comprise one or more of: a MAC CE activation command, an RRCmessage, and/or DCI. The reconfiguration message may indicate a TCIstate for the first cell. The wireless device may use the TCI state foreach cell in the plurality of cells. The wireless device may use the TCIstate to change from the first serving beam to the second serving beamfor each cell in the plurality of cells.

Based on the wireless device using the TCI state for a first cell toreconfigure operation related to each cell in the plurality of cells(e.g., a cell group comprising the first cell), various advantages maybe achieved, including, for example, reduced latency, reduced powerconsumption, and reduced signaling overhead. Signaling overhead relatedto switching from the first serving beam to the second serving beam foreach cell in the plurality of cells may be reduced, for example, basedon the wireless device using the TCI state for the first cell toreconfigure operation related to each cell in the plurality of cells.Signaling overhead may be reduced by using one reconfiguration message(e.g., a MAC CE activation command, an RRC message, and/or DCI) toreconfigure operation related to each cell in the plurality of cells incomparison to using a separate reconfiguration message (e.g., separateMAC CE activation command(s) and/or two or more MAC CE activationcommands, RRC, and/or DCI) for each cell in the plurality of cells.Interference (e.g., to and/or experienced by one or more wirelessdevices) may be reduced by reducing signaling overhead. Communicationbetween the wireless device and each cell of the plurality of cells mayresume more expeditiously based on the wireless device using the TCIstate for the first cell to reconfigure operation of each cell in theplurality of cells. Latency related to beam management for each cell inthe plurality of cells may be reduced by using one reconfigurationmessage (e.g., an MAC CE activation command, RRC message, and/or DCI) toreconfigure operation related to each cell in the plurality of cells incomparison to using a separate reconfiguration message (e.g., separateMAC CE activation command(s) and/or two or more MAC CE activationcommands, RRC message, and/or DCI) for each cell in the plurality ofcells. Consumption of the power source (e.g., the battery) of thewireless device may be reduced based on the wireless device using theTCI state for the first cell to reconfigure operation of each cell inthe plurality of cells. Consumption of the power source may be reducedby obviating power consumption related to receiving, processing, and/ordecoding any reconfiguration message other than the one reconfigurationmessage used to reconfigure operation related to each cell in theplurality of cells.

A wireless device may perform a BFR procedure on an SpCell (e.g., PCellor PSCell). A base station may send (e.g., transmit), to a wirelessdevice, one or more messages comprising configuration parameters of oneor more cells. The one or more cells may comprise at least onePCell/PSCell and/or one or more SCells. An SpCell (e.g., PCell orPSCell) and one or more SCells may operate on different frequenciesand/or different bands.

An SCell of the one or more SCells may support a multi-beam operation. Awireless device may perform one or more beam management procedures(e.g., a BFR procedure) on or for the SCell, for example, based on theSCell supporting multi-beam operation. The wireless device may perform aBFR procedure for the SCell, for example, if at least one of one or morebeam pair links between the SCell and the wireless device fails. CertainBFR procedures may result in inefficiencies based on a beam failure forthe SCell. Certain BFR procedures may be inefficient, take a long time,and/or increase battery power consumption.

Downlink radio efficiency may be improved and/or uplink signalingoverhead may be reduced, for example, if a beam failure occurs for oneor more SCells based on one or more BFR procedures described herein.Random access resources of a first cell may be used, for example, if abeam failure occurs for an SCell of one or more SCells. Downlinksignaling processes may be enhanced for recovery of a beam failure foran SCell. Uplink signaling may be enhanced for a BFR procedure of theSCell.

A BFR procedure for an SCell may be provided based on the one or moreBFR procedures described herein. A duration of the BFR procedure may bereduced and/or battery power consumption may be reduced based on the oneor more BFR procedures described herein.

A wireless device may be configured, by a base station, with an SCell.The SCell may not have uplink resources. The SCell may comprise downlinkresources. The wireless device may not transmit an uplink signal (e.g.,preamble) for a BFR procedure of the SCell on the SCell, for example,based on not having uplink resources and/or if the wireless devicedetects a beam failure on the SCell. The wireless device may not performa BFR procedure on the SCell. The base station may not be aware of thebeam failure on the SCell based on the wireless device not performingthe BFR procedure. A BFR procedure may be provided, for example, if anSCell comprises downlink-only resources based on the one or more BFRprocedures described herein.

An SCell may operate in a high frequency (e.g., 23 GHz, 60 GHz, 70 GHz,or any other frequency such as a frequency greater than a lowfrequency). An SpCell may operate in a low frequency (e.g., 2.4 GHz, 5GHz, or any other frequency such as a frequency less than a highfrequency). A channel condition of the SCell may be different from achannel condition of the SpCell. The wireless device may use uplinkresources of the SpCell to send (e.g., transmit) a preamble for a BFRrequest for the SCell, for example, to improve robustness oftransmission of the preamble. A BFR procedure may be provided, forexample, if an SCell operates in a different frequency than a PCell. ABFR procedure may be provided, for example, if an SCell used uplinkresources (e.g., random access resources, uplink BWPs of the PCell) ofthe PCell for a BFR procedure of the SCell.

FIG. 24 shows an example of BWP configurations for BFR procedure. Afirst cell 2402 may comprise one or more UL BWPs (e.g., UL-BWP-1 2404,UL-BWP-2 2406, and/or UL-BWP-3 2408). A second cell 2410 may compriseone more DL BWPs (e.g., DL-BWP-3 2412 and/or DL-BWP-4 2414). A basestation may allocate UL resources of a UL BWP (e.g., UL-BWP-1) for abeam failure recovery request (BFRQ) and/or a SR. The base station mayallocate UL resources of a UL BWP (e.g., UL-BWP-2) for a BFRQ without aSR. The base station may allocate UL resources of a UL BWP (e.g.,UL-BWP-3) for a SR without a BFRQ. The base station may allocate DLresources of a DL BWP for radio link monitoring. The base station maysend a radio link monitoring configuration (e.g., RLM configuration) toa wireless device that configures the wireless device to use a set ofresource indexes for radio link monitoring.

A wireless device may receive, from a base station, one or more messagescomprising one or more configuration parameters for a first cell 2402(e.g., PCell, PSCell, PUCCH SCell, SCell) and one or more secondarycells 2410 (e.g., SCell). The one or more secondary cells may comprise asecond cell (e.g., SCell). The one or more messages may comprise one ormore RRC messages (e.g. RRC connection reconfiguration message, RRCconnection reestablishment message, and/or RRC connection setupmessage).

The one or more configuration parameters may comprise BWP configurationparameters for a plurality of BWPs. The plurality of BWPs may comprise afirst plurality of UL BWPs of the first cell. The first plurality of ULBWPs (e.g., UL-BWP-1 2404, UL-BWP-2 2406, and UL-BWP-3 2408) maycomprise a first uplink BWP. The first uplink BWP may be UL-BWP-1 2404.The first uplink BWP may be UL-BWP-2 2406. The first uplink BWP may beUL-BWP-3 2408.

The first uplink BWP may be UL-BWP-1 2404 and/or UL-BWP-2 2406. Thefirst uplink BWP may be UL-BWP-1 2404 and/or UL-BWP-3 2408. The firstuplink BWP may be UL-BWP-2 2406 and UL-BWP-3 2408. The first uplink BWPmay be UL-BWP-1 2404, UL-BWP-2 2406, and UL-BWP-3 2408. The plurality ofBWPs may comprise a second plurality of DL BWPs of the second cell 2410.The second plurality of DL BWPs (e.g., DL-BWP-3 2412 and DL-BWP-4 2414)may comprise a second downlink BWP. The second downlink BWP may beDL-BWP-3 2412. The second downlink BWP may be DL-BWP-4 2414. The seconddownlink BWP may be DL-BWP-3 2412 and/or DL-BWP-4 2414.

The one or more configuration parameters may comprise BWP specificindices for the plurality of BWPs (e.g., provided by a parameter such asa higher layer parameter bwp-ID in the one or more configurationparameters). Each BWP of the plurality of BWPs may be indicated (e.g.,identified) using a corresponding BWP specific index of the BWP specificindices. The first uplink BWP of the first plurality of UL BWPs may beindicated (e.g., identified) using a first uplink BWP specific index.The second downlink BWP of the second plurality of DL BWPs may beindicated (e.g., identified) using a second downlink BWP specific index.The one or more configuration parameters may comprise DL-BWP-specificBFR configuration parameters (e.g., RadioLinkMonitoringConfig orRLMConfig in FIG. 24 ) for the second downlink BWP (e.g., DL-BWP-3 2412and/or DL-BWP-4 2414).

The DL-BWP-specific BFR configuration parameters for the second downlinkBWP (e.g., DL-BWP-3 2412) of the second cell may comprise one or moresecond RSs (e.g., configured by a RadioLinkMonitoringRS parameter) ofthe second downlink BWP and/or a second BFI counter (e.g.,beamFailureInstanceMaxCount). The wireless device may detect a beamfailure of the second downlink BWP based on the one or more second RSs(e.g., SSBs, periodic CSI-RSs, etc.). The wireless device may assess(e.g., analyze, monitor, determine, etc.) the one or more second RSs todetect the beam failure of the second downlink BWP.

The one or more configuration parameters may comprise BWP-specific BFRconfiguration parameters (e.g., BeamFailureRecoveryConfig or BFRConfig)for the second downlink BWP (e.g., DL-BWP-3 2412) of the second cell TheBWP-specific BFR configuration parameters may comprise at least one of:one or more second candidate RSs (e.g., candidateBeamRSList), a secondthreshold (e.g., rsrp-ThresholdSSB), and/or a second beam failurerecovery timer (e.g., beamFailureRecoveryTimer). The base station mayconfigure the BWP-specific BFR configuration parameters on the seconddownlink BWP. The base station may configure the BWP-specific BFRconfiguration parameters on at least one UL BWP of the first pluralityof UL BWPs of the first cell.

The base station may configure the BWP-specific BFR configurationparameters, for example, based on uplink being configured for the secondcell and/or for at least one UL BWP of a second plurality of UL BWPs ofthe plurality of BWPs on the second cell. The second downlink BWPspecific index and an uplink BWP specific index associated with the atleast one UL BWP may be the same. The wireless device may determine acandidate RS (and/or a candidate beam), for example, based on assessing(e.g., analyzing, monitoring, determining, etc.) the one or more secondcandidate RSs (e.g., SSBs, periodic CSI-RSs) to select a candidate RS(or a candidate beam) for a BFR procedure of the second downlink BWP.The wireless device may use the BWP-specific BFR configurationparameters for a BFR procedure of the second downlink BWP.

The one or more configuration parameters may indicate a third threshold(e.g., rlmInSyncOutOfSyncThreshold). The wireless device may use thethird threshold for detecting a beam failure of a downlink BWP (e.g.,the second downlink BWP) of the second cell. A physical layer of thewireless device may assess (e.g., analyze, monitor, determine, etc.) aradio link quality of (or according to) the one or more second RSs(e.g., RadioLinkMonitoringRS) of the second downlink BWP. The radio linkquality (e.g., of one or more or each of the one or more second RSs) maybe worse (e.g., higher BLER, lower SINR, lower L1-RSRP) than the thirdthreshold. The physical layer may provide a BFI indication to a higherlayer (e.g. MAC) of the wireless device, for example, based on or inresponse to the radio link quality being worse than the third threshold.

The third threshold (e.g. Qout,LR) may correspond to a default value ofhigher layer parameter RLM-IS-OOS-thresholdConfig (e.g.,rlmInSyncOutOfSyncThreshold). The higher layer (e.g., MAC) of thewireless device may increment a beam failure indicator counter (e.g.,BFI_COUNTER) by one, for example, based on or in response to thephysical layer providing the BFI indication (such as at time T 2200, 2T2202, and/or 5T 2208 in FIG. 22 ). The beam failure indicator counter(e.g., BFI_COUNTER) may be a counter for a beam failure instanceindication. The beam failure indicator counter (e.g., BFI_COUNTER) maybe initially set to zero or any other value (e.g., number).

The beam failure indicator counter (e.g., BFI_COUNTER) may be equal toor greater than the second BFI counter (e.g.,beamFailureInstanceMaxCount). The base station may configure theBWP-specific BFR configuration parameters (e.g.,BeamFailureRecoveryConfig) for the second downlink BWP. The wirelessdevice may start the second BFR timer, if configured, for example, basedon or in response to: the beam failure indicator counter (e.g.,BFI_COUNTER) being equal to or greater than the second BFI counter,and/or the base station configuring the BWP-specific BFR configurationparameters.

The wireless device may detect a beam failure of the second downlink BWPof the second cell, for example, based on or in response to the beamfailure indicator counter (e.g., BFI_COUNTER) being equal to or greaterthan the second BFI counter. The wireless device may initiate a BFRprocedure for the second downlink BWP, for example, based on or inresponse to the detecting the beam failure of the second downlink BWP.The wireless device may start the second BFR timer, for example, basedon to initiating the BFR procedure.

Initiating the BFR procedure for the second downlink BWP may comprisetriggering a BFRQ for the BFR procedure for the second downlink BWP. Thewireless device may trigger a BFRQ for a BFR procedure for the seconddownlink BWP, for example, based on or in response to the detecting thebeam failure of the second downlink BWP. The BFRQ may be pending untilthe wireless device cancels the BFRQ, for example, based on the wirelessdevice triggering a BFRQ.

The wireless device may be configured (e.g., by the one or moreconfiguration parameters) with the one or more second candidate RSs(e.g., candidateBeamRSList) for the second downlink BWP. The wirelessdevice may initiate a candidate beam selection for the BFR procedure ofthe second downlink BWP, for example, based on or in response to beingconfigured with the one or more second candidate RSs. The candidate beamselection may comprise determining (e.g., selecting, indicating, and/oridentifying) a candidate RS (e.g., CSI-RS, SS/PBCH blocks) in the one ormore second candidate RSs of the second downlink BWP. The candidate RSmay be associated with a candidate RS index (e.g., periodic CSI-RSconfiguration indexes and/or the SSB indexes provided by the one or moreconfiguration parameters).

A wireless device (e.g., a physical layer of a wireless device) mayassess (e.g., analyze, monitor, determine, etc.) a second radio linkquality (e.g., BLER, L1-RSRP) of the one or more second candidate RSs,for example, during the candidate beam selection. At least one of theone or more second candidate RSs may have a second radio link qualitybetter (e.g. lower BLER or higher L1-RSRP or higher SINR) than thesecond threshold parameter (e.g., rsrp-ThresholdSSB).

The wireless device (e.g., the physical layer of the wireless device)may provide, to a higher layer (e.g., MAC) of the wireless device, anindex of the at least one of the one or more second candidate RSs and/orthe second radio link quality (e.g., L1-RSRP) of the at least one of theone or more second candidate RSs. The one or more configurationparameters may indicate the index. The wireless device (e.g., the higherlayer (e.g., MAC) of the wireless device) may select the candidate RSamong the at least one of the one or more second candidate RSs, forexample, based on or in response to: receiving the index of the at leastone of the one or more second candidate RSs, and/or the second radiolink quality of the at least one of the one or more second candidateRSs.

The wireless device (e.g., the higher layer (e.g., MAC) of the wirelessdevice) may initiate the candidate beam selection, for example, based onor in response to the BFI_COUNTER being equal to or greater than thesecond BFI counter. Initiating the candidate beam selection may compriserequesting, by the higher layer (e.g., MAC) from the physical layer ofthe wireless device, an index of at least one of the one or more secondcandidate RSs and/or a second radio link quality (e.g., L1-RSRP) of theat least one of the one or more second candidate RSs. The second radiolink quality may be better (e.g. lower BLER or higher L1-RSRP or higherSINR) than the second threshold parameter (e.g., rsrp-ThresholdSSB).

The wireless device may trigger a BFRQ in response to the determining(e.g., selecting, indicating, and/or identifying) the candidate RS forthe BFR procedure for the second downlink BWP of the second cell. Theone or more configuration parameters may comprise a BFRQ configurationfor the first cell. The BFRQ configuration may indicate one or more BFRQtransmission occasions. The one or more BFRQ transmission occasions maybe periodic (e.g., the periodicity may be indicated by the BFRQconfiguration). The wireless device may be allowed to send (e.g.,transmit) a BFRQ using the one or more BFRQ transmissions occasions, forexample, based on being triggered.

The BFRQ configuration may indicate at least one of: a prohibit timer(e.g., bfrq-ProhibitTimer, sr-ProhibitTimer), a maximum quantity of BFRQtransmissions (e.g., bfrq-TransMax, sr-TransMax), and/or a periodicityand/or offset of a BFRQ transmission occasion of the one or more BFRQtransmission occasions. The wireless device may not send (e.g.,transmit) a BFRQ for the BFRQ configuration, for example, during runningof the prohibit timer. A wireless device may use (e.g., maintain) a BFRQtransmission counter (e.g., BFRQ_COUNTER) associated with the BFRQconfiguration. The wireless device may transmit, and/or re-transmit, aBFRQ at least until the BFRQ transmission counter is less than themaximum quantity of BFRQ transmissions.

A first BFRQ of a BFRQ configuration may be triggered. A second BFRQ, ofthe BFRQ configuration, may not be pending. The wireless device may setthe BFRQ transmission counter of the BFRQ configuration to zero, one orany other value, for example, based on or in response to the first BFRQbeing triggered and the second BFRQ not being pending. The BFRQconfiguration may indicate one or more first uplink physical channels(e.g., BFRQ of UL-BWP-1 2404 and UL-BWP-2 2406 in FIG. 24 ) of the firstcell 2402. The one or more first uplink physical channels may beassociated with (e.g., dedicated to, assigned to) the wireless device.The one or more first uplink physical channels may comprise randomaccess resources (e.g., PRACH resource(s)), uplink control channelresources (e.g., PUCCH resource(s)), and/or uplink shared channelresources (e.g., PUSCH resource(s)).

The wireless device may use the one or more first uplink physicalchannels for a BFR procedure of at least one secondary cell (e.g., thesecond cell 2410) of the one or more secondary cells. The wirelessdevice may send (e.g., transmit) a BFRQ via at least one uplink physicalchannel (e.g., BFRQ of UL-BWP-1 2404 or UL-BWP-2 2406 in FIG. 24 ) ofthe one or more first uplink physical channels for the BFR procedure ofthe at least one secondary cell, for example, based on the wirelessdevice detecting a beam failure of the at least one secondary cell. Thebase station may be informed of the BFR procedure of the at least onesecondary cell, for example, based on the base station receiving theBFRQ via the at least one uplink physical channel (e.g., PUCCHresource). The wireless device may send (e.g., transmit) a pending BFRQfor example, based on the one or more BFRQ transmission occasions andthe one or more first uplink physical channels.

At least one uplink physical channel (e.g., BFRQ of UL-BWP-1 2404 inFIG. 24 ) of the one or more first uplink physical channels may beconfigured for a first uplink BWP (e.g., UL-BWP-1 2404) of the firstplurality of UL BWPs of the first cell. The BFRQ may be pending. Thewireless device may determine that the first uplink BWP is an activeuplink BWP of the first cell at the time of a BFRQ transmission occasionof the one or more BFRQ transmission occasions, for example, based onthe BFRQ pending. The at least one uplink physical channel (e.g., PUCCHresource) on the first uplink BWP may be valid, for example, based onthe determining that the first uplink BWP is an active uplink BWP of thefirst cell at the time of a BFRQ transmission occasion. The at least oneuplink physical channel (e.g., PUCCH resource) on the first uplink BWPmay be determined to be (e.g., considered as) valid, for example, basedon determining that the first uplink BWP is an active uplink BWP of thefirst cell at the time of a BFRQ transmission occasion. The wirelessdevice may send (e.g., transmit) the BFRQ via the at least one uplinkphysical channel, for example, based on the wireless device having theBFRQ transmission occasion on the valid at least one uplink physicalchannel. The at least one uplink physical channel may comprise one ormore first time resources and/or one or more first frequency resources.

The one or more configuration parameters may comprise a SRconfiguration. The SR configuration may indicate one or more seconduplink physical channels (e.g., SR of UL-BWP-1 2404 and UL-BWP-3 2408 inFIG. 24 ). The one or more second uplink physical channels may be partthe first cell 2402 and/or at least one secondary cell of the one ormore secondary cells. The wireless device may use the one or more seconduplink physical channels for requesting uplink shared channel (UL-SCH)resources for an uplink transmission. The base station may be informed(e.g., receive an indication) of the request for uplink shared resources(e.g., UL-SCH resource(s)), for example, based on the base stationreceiving an SR via at least one second uplink physical channel (e.g.,PUCCH resource) of the one or more second uplink physical channels(e.g., SR via UL-BWP-1 2404 and UL-BWP-3 2408 in FIG. 24 ).

The wireless device may use the one or more second uplink physicalchannels for a BFR procedure of at least one secondary cell (e.g., thesecond cell) of the one or more secondary cells, which may be inaddition to using for requesting UL-SCH resources for an uplinktransmission. The wireless device may send (e.g., transmit) an uplinkrequest (e.g., BFRQ, SR) via at least one second uplink physical channel(e.g., SR of UL-BWP-1 or UL-BWP-3 in FIG. 24 ) of the one or more seconduplink physical channels for the BFR procedure of the at least onesecondary cell, for example, based on the wireless device detecting abeam failure of the at least one secondary cell. The base station maynot determine (e.g., distinguish) whether the uplink request istransmitted for the BFR procedure or for requesting UL-SCH resources,for example, based on the base station receiving the uplink request viathe at least one second uplink physical channel resource (e.g., PUCCHresource).

The SR configuration may indicate one or more SR transmission occasions.The one or more SR transmission occasions may be periodic (e.g., theperiodicity may be indicated by the SR configuration). The wirelessdevice may be allowed to send (e.g., transmit) a pending SR, forexample, using (e.g., during) the one or more SR transmissionsoccasions.

The wireless device may use the one or more second uplink physicalchannels for the BFR procedure. At least one second uplink physicalchannel (e.g., SR of UL-BWP-1 2404 in FIG. 24 ) of the one or moresecond uplink physical channels (e.g., SR of UL-BWP-1 2404 and UL-BWP-32408 in FIG. 24 ) may be configured for a first uplink BWP (e.g.,UL-BWP-1 2404) of the first plurality of UL BWPs of the first cell 2402.The BFRQ may be pending. The wireless device may determine that thefirst uplink BWP is an active uplink BWP of the first cell before an SRtransmission occasion of the one or more SR transmission occasions, forexample, based on the BFRQ pending. The at least one second uplinkphysical channel (e.g., PUCCH resource) of the first uplink BWP may bevalid, for example, based on the determining that the first uplink BWPis an active uplink BWP of the first cell. The at least one uplinkphysical channel (e.g., PUCCH resource) of the first uplink BWP may beconsidered valid, for example, based on the determining that the firstuplink BWP is an active uplink BWP of the first cell. The wirelessdevice may send (e.g., transmit) an uplink request (e.g., the BFRQ) viathe valid at least one second uplink physical channel, for example,based on the wireless device having the SR transmission occasion via theat least one second uplink physical channel (e.g., PUCCH resource). Theat least one second uplink physical channel may comprise one or moresecond time resources and/or one or more second frequency resources.

Using the one or more first uplink physical channels for a BFR proceduremay reduce the latency of the BFR procedure. The base station may beaware of the BFR procedure in time. The base station may send (e.g.,transmit) an uplink grant for the BFR procedure. The uplink grant mayindicate uplink resources enough to include a BFR MAC CE for the BFRprocedure. The wireless device may not send (e.g., transmit) a bufferstatus report (BSR), for example, based on or in response to the usingthe one or more first uplink physical channels. The wireless device maysend (e.g., transmit) a buffer status report (BSR) in response to theusing the one or more second uplink physical channels.

FIG. 25A and FIG. 25B show examples of active BWP configurationscenarios for a BFR procedure for a secondary cell secondary cell. Afirst cell 2502 may comprise one or more UL BWPs (e.g., UL-BWP-1 2502,UL-BWP-2 2506, and/or UL-BWP-3 2508). A second cell 2510 may compriseone more DL BWPs (e.g., DL-BWP-3 2512 and/or DL-BWP-4 2514). A basestation may allocate UL resources of a UL BWP (e.g., UL-BWP-1) for BFRQand SR. The base station may allocate UL resources of a UL BWP (e.g.,UL-BWP-2) for SR without BFRQ. The base station may allocate no ULresources of a UL BWP (e.g., UL-BWP-3) for SR or BFRQ. The base stationmay allocate DL resources of a DL BWP for radio link monitoring. Thebase station may send a radio link monitoring configuration (e.g., RLMconfiguration) to a wireless device that configures the wireless deviceto use a set of resource indexes for radio link monitoring.

A wireless device may use a BFR procedure for BFR of a second cell toavoid or reduce a potential cost in time, dropped calls, and delaysassociated with declaring a radio link failure. A BFR procedure mayprevent a wireless device from declaring a radio link failure (RLF), forexample, by detecting and recovering a communication loss earlier as anRLF procedure tries to reestablish connection with the base station. ARLF procedure may be a long process and may interrupt the datacommunication. Using another cell (e.g., PCell) for a BFR procedure ofan SCell may be useful, for example, because PCells may operate in lowfrequencies. Low frequencies may be more reliable compared to highfrequencies at which SCells operate. Transmission via PCell may be morelikely to be received by a base station. The base station may takemeasures to recover the beam failure of the SCell faster and/or earlier.Using normal SR resources instead of falling back to a random-accessprocedure may be faster, for example, based on BFRQ resources not beingconfigured. Normal SR resources may be using contention-free resources.The base station may give a wireless device an uplink grant to transmitBFR MAC CE via normal SR resources earlier, for example, than comparedto a random-access procedure. Fast beam failure recovery procedure maybe important, for example, as the duration of the BFR procedureincreases, a probability of declaring RLF increases.

A wireless device may receive a configuration indicating uplinkresources of a first cell for BFR and/or SRs. The wireless device maydetermine a second cell has a beam failure and perform a BFR procedure(e.g., SCell BFR procedure). The wireless device may determine that anactive BWP of the first cell is not configured to use uplink resourcesfor a BFR (e.g., SR-like PUCCH resources, PUCCH-BFR resources, dedicatedPUCCH resources for SCell BFR, etc.). The wireless device may determinean uplink resource configured for a SR to report the BFR. The wirelessdevice may send a SR message using the uplink resource configured forSR. The wireless device may receive an uplink grant, based on the SRmessage. The wireless device may report the beam failure to the basestation, for example, based on the uplink grant.

The wireless device may determine an uplink configuration from aplurality of uplink configurations configured for SR, for example, basedon a data type, characteristic, lowest transmission counter or timing ofthe uplink configuration. The wireless device may select the uplinkconfiguration from the uplink configurations configured for SR, forexample, based on a SR for Ultra Reliable Low Latency Communications(URLLC), an SR for a highest logical channel priority of availableuplink control resources, a first-in-time SR, a SR used with enhancedMobile Broadband (eMBB), and/or an SR associated with an uplink grant ofsufficient size to send the beam failure information (e.g., BFR MAC CE).

The wireless device may receive, for an uplink bandwidth part (UL BWP)of a first cell, a SR configuration that indicates uplink resourcesdedicated to BFR of a second cell and/or uplink resources configured forscheduling requests. The SR configuration may comprise a field thatindicates which SR resources are used for BFR. The SR configuration maycomprise a field indicating whether one or more second uplink physicalchannels associated with the SR configuration can be used for a BFRprocedure of at least one secondary cell of one or more secondary cells.

The wireless device may switch UL BWPs from a first UL BWP to a secondUL BWP, for example, during a BFR procedure. The wireless device mayperform this switching autonomously or based on instructions from thebase station. The wireless device may determine a second cell has a beamfailure and perform a BFR procedure. The wireless device may performnone or part of the BFR procedure before switching UL BWPs. The wirelessdevice may switch an active UL BWP from a first UL BWP to a second ULBWP. The wireless device may reset a SR prohibit timer and/or BFRQtransmission counter, for example, based on the switching of the activeUL BWPs. The wireless device may continue the BFR procedure by sendingan uplink signal to the base station using an uplink resource configuredfor BFR or SR.

FIG. 25A shows at least one uplink physical channel (e.g., BFRQ ofUL-BWP-1 2504) of the one or more first uplink physical channels may beconfigured for the first uplink BWP (e.g., UL-BWP-1 2504) of the firstcell 2502. The BFRQ may be pending for the BFR procedure of the seconddownlink BWP of the second cell. The first uplink BWP of the first cellmay be an active uplink BWP of the first cell, for example, based on theBFRQ pending. The wireless device may determine that the first uplinkBWP is an active uplink BWP of the first cell at the time of a BFRQtransmission occasion of the one or more BFRQ transmission occasions.The at least one uplink physical channel resource (e.g., PUCCH resource)of the first uplink BWP may be valid, for example, based on thedetermining that the first uplink BWP is an active uplink BWP of thefirst cell. The wireless device may send (e.g., transmit) the BFRQ viathe valid at least one uplink physical channel for the BFR procedure ofthe second downlink BWP of the second cell, for example, based on theBFRQ pending and/or the wireless device having the BFRQ transmissionoccasion on the valid at least one uplink physical channel. The at leastone uplink physical channel resource (e.g., PUCCH resource) for the BFRQtransmission occasion may not overlap with a measurement gap. The atleast one uplink physical channel resource (e.g., PUCCH resource) forthe BFRQ transmission occasion may not overlap with an uplink sharedresource (e.g., UL-SCH resource). The prohibit timer may not be runningduring the BFRQ transmission occasion. The wireless device may start theprohibit timer, for example, based on or in response to the sending(e.g., transmitting) the BFRQ. The wireless device may increment theBFRQ transmission counter (e.g., BFRQ_COUNTER) by one, two or any otherquantity, for example based on or in response to the sending (e.g.,transmitting) the BFRQ.

FIG. 25B shows an example of downlink BFR procedure for a secondarycell. The wireless device may determine that at least one uplinkphysical channel resource (e.g., PUCCH resource for the BFRQ) of the oneor more first uplink physical channels (e.g., indicated by the BFRQconfiguration) is not configured for a second uplink BWP (e.g., UL-BWP-22506) of the first plurality of UL BWPs of the first cell. The BFRQ maybe pending for the BFR procedure of the second downlink BWP of thesecond cell. The second uplink BWP (e.g., UL-BWP-2 2506) may be anactive uplink BWP of the first cell, for example, based on the BFRQpending. The wireless device may determine that the second uplink BWPmay be an active uplink BWP of the first cell at the time of a BFRQtransmission occasion of the one or more BFRQ transmission occasions.

The wireless device may fall back to an SR transmission, for examplebased on the second uplink BWP being the active uplink BWP of the firstcell and/or determining that the at least one uplink physical channel(e.g., PUCCH resource for the BFRQ) of the one or more first uplinkphysical channels is not configured for the second uplink BWP. Thewireless device may fall back to an SR transmission, for example, basedon the second uplink BWP being the active uplink BWP of the first cell,the wireless device not having the at least one uplink physical channelof the one or more first uplink physical channels, and/or the pendingBFRQ on the second uplink BWP.

An uplink BWP (e.g., UL-BWP-2 2506) of a cell (e.g., the first cell2502) may be an active uplink BWP, for example, based on the BFRQpending. In at least some examples, only one uplink BWP may be an activeuplink BWP, for example, based on the BFRQ pending. Alternatively, morethan one uplink BWP (e.g., any quantity of uplink BWPs) may be an activeuplink BWP. One or more cells may have one active uplink BWP. The cellmay one active uplink BWP in normal uplink carrier (NUL) and one activeuplink BWP in a supplementary uplink carrier (SUL). A cell may twoactive uplink BWPs, for example, based on having a SUL. The cell may bethe first cell 2502. The uplink BWP may be the second uplink BWP (e.g.,UL-BWP-2 2506) of the first cell. The cell may be one of the one or moreor secondary cells. The uplink BWP may be one active uplink BWP of theone of the one or more secondary cells. At least one second uplinkphysical channel resource (e.g., SR of UL-BWP-2 2506 in FIG. 25B) of theone or more second uplink physical channels (e.g., indicated by the SRconfiguration) may be configured for the one uplink BWP of the cell. Thewireless device may determine that the uplink BWP may be an activeuplink BWP of the cell before a SR transmission occasion of one or moreSR transmission occasions (e.g., indicated by the SR configuration). Theat least one second uplink physical channel resource (e.g., PUCCHresource) of the uplink BWP (e.g., the one uplink BWP) may be valid, forexample, based on the determining that the uplink BWP (e.g., the oneuplink BWP) may be an active uplink BWP of the cell. The wireless devicemay send (e.g., transmit) an uplink request (e.g., the BFRQ) via thevalid at least one second uplink physical channel for the BFR procedureof the second downlink BWP of the second cell, for example, based on theBFRQ pending and/or the wireless device having the SR transmissionoccasion for the valid at least one second uplink physical channel. Thefalling back to the SR transmission may comprise sending (e.g.,transmitting) the uplink request (e.g., the BFRQ) via the valid at leastone second uplink physical channel (e.g., indicated by the SRconfiguration) for the BFR procedure of the second downlink BWP of thesecond cell.

The wireless device may send (e.g., transmit) the uplink request (e.g.,BFRQ) via the valid at least one second uplink physical channel for theBFR procedure of the second downlink BWP of the second cell, forexample, based on the BFRQ pending and/or the wireless device fallingback to the SR transmission. The wireless device may fall back to the SRtransmission, for example, based on the active second uplink BWP of thefirst cell not being configured with the at least one uplink physicalchannel and the active one uplink BWP of the cell being configured withthe at least one second uplink physical channel. The wireless device mayuse the SR transmission occasion of the at least one second uplinkphysical channel of the one uplink BWP. The at least one second uplinkphysical channel resource (e.g., PUCCH resource) for the SR transmissionoccasion may not overlap with a measurement gap. The at least one seconduplink physical channel resource (e.g., PUCCH resource) for the SRtransmission occasion may not overlap with an UL-SCH resource. An SRprohibit timer indicated by the SR configuration may not be running atthe time of the SR transmission occasion.

At least one uplink physical channel resource (e.g., PUCCH resource forthe BFRQ) of the one or more first uplink physical channels (e.g.,indicated by the BFRQ configuration) may not be configured for a thirduplink BWP (e.g., UL-BWP-3 2508) of the first plurality of UL BWPs ofthe first cell. At least one second uplink physical channel (e.g., SR ofUL-BWP-2 2506) of the one or more second uplink physical channels (e.g.,indicated by the SR configuration) may not be configured for the oneuplink BWP (e.g., UL-BWP-3 2508). The uplink BWP (e.g., the one uplinkBWP) of the cell may be the active uplink BWP of the cell, for example,based on the BFRQ pending. The BFRQ may be pending for the BFR procedureof the second downlink BWP of the second cell. The third uplink BWP(e.g., UL-BWP-3 2508) of the first cell may be an active uplink BWP ofthe first cell, for example, based on the BFRQ pending. The wirelessdevice may fall back to a random access procedure (e.g.,contention-based random access procedure) for the BFR procedure of thesecond downlink BWP of the second cell, for example, based on the BFRQpending, the third uplink BWP not being configured with the at least oneuplink physical channel, and/or the one uplink BWP not being configuredwith the at least one second uplink physical channel. The falling backto the random access procedure may comprise initiating the random accessprocedure by sending (e.g., transmitting) a random access preamble via arandom access resource (e.g., PRACH resource) of the third UL BWP of thefirst cell for the BFR procedure of the second downlink BWP of thesecond cell. The wireless device may cancel the BFRQ, for example, basedon or in response to initiating the random access procedure. Thewireless device may not cancel the BFRQ, for example, based on thewireless device initiating the random access procedure. The wirelessdevice may keep the BFRQ pending, for example, based on the wirelessdevice initiating the random access procedure.

An active uplink BWP of the first cell may not comprise at least oneuplink physical channel of the one or more first uplink physicalchannels, for example, based on the BFRQ pending. One or more activeuplink BWPs of one or more cells of the first cell and the one or moresecondary cells may not comprise at least one second uplink physicalchannel of the one or more second uplink physical channels, for example,based on the BFRQ pending. One or more cells may comprise the first celland one or more of the one or more secondary cells. The wireless devicemay fall back to a random access procedure (e.g., contention-basedrandom access procedure) for the BFR procedure of the second downlinkBWP of the second cell, for example, based on the active uplink BWP ofthe first cell not comprising the at least one uplink physical channelresource and/or one or more active uplink BWPs of one or more cells notcomprising the at least one second uplink physical channel resource.

FIG. 26 shows an example of an active BWP configuration scenario fordownlink BFR procedure for a secondary cell. A first cell 2602 maycomprise one or more UL BWPs (e.g., UL-BWP-1 2604, UL-BWP-2 2606, and/orUL-BWP-3 2608). A second cell 2610 may comprise one more DL BWPs (e.g.,DL-BWP-3 2612 and/or DL-BWP-4 2614). A base station may allocate ULresources of a UL BWP (e.g., UL-BWP-1) for BFRQ and SR. The base stationmay allocate UL resources of a UL BWP (e.g., UL-BWP-2) for SR withoutBFRQ. The base station may allocate no UL resources of a UL BWP (e.g.,UL-BWP-3) for SR or BFRQ. The base station may allocate DL resources ofa DL BWP for radio link monitoring. The base station may send a radiolink monitoring configuration (e.g., RLM configuration) to a wirelessdevice that configures the wireless device to use a set of resourceindexes for radio link monitoring.

The one or more configuration parameters may comprise one or more SRconfigurations (e.g., SR₁ and SR₂) comprising a first SR configuration(e.g., SRO and a second SR configuration (e.g., SR₂) for one uplink BWP(e.g., the first uplink BWP, UL-BWP-2 2606) of a cell (e.g., the firstcell 2602). A BFRQ may be pending for the BFR procedure of the seconddownlink BWP of the second cell. The wireless device may fall back to anSR transmission. The one uplink BWP (e.g., UL-BWP-2 2606) of the cellmay be an active uplink BWP of the cell, for example, based on the BFRQpending. The wireless device may select at least one SR configuration(e.g., SR₁ and/or SR₂ among the one or more SR configurations, forexample, based on the falling back to the SR transmission. The at leastone SR configuration (e.g., SR₁ may indicate one or more selected uplinkphysical channels (e.g., SR₁ of UL-BWP-1 2604 and UL-BWP-2 2606). The atleast one SR configuration may indicate one or more selected SRtransmission occasions.

At least one selected uplink physical channel of the one or moreselected uplink control physical channels may be configured for the oneuplink BWP of the cell. The wireless device may determine that the oneuplink BWP may be an active uplink BWP of the cell at the time of an SRtransmission occasion of the one or more selected SR transmissionoccasions. The at least one selected uplink physical channel resource(e.g., PUCCH resource) of the one uplink BWP may be valid, for example,based on determining that the one uplink BWP may be an active uplink BWPof the cell. The wireless device may send (e.g., transmit) an uplinkrequest (e.g., BFRQ) via the valid at least one selected uplink physicalchannel for the BFR procedure of the second downlink BWP of the secondcell, for example, based on the BFRQ pending and/or the wireless devicehaving the SR transmission occasion of the valid at least one selecteduplink physical channel of the one uplink BWP, The at least one selecteduplink physical channel resource (e.g., PUCCH resource) for the SRtransmission occasion may not overlap with a measurement gap. The atleast one selected uplink physical channel resource (e.g., PUCCHresource) for the SR transmission occasion may not overlap with a uplinkshared resource (e.g., UL-SCH resource).

The determining (e.g., selecting) may be based on a logical channelpriority. A logical channel with a highest priority may be mapped to atleast one SR configuration of the one or more SR configurations. Thelogical channel may be for a URLLC service or eMBB service. The wirelessdevice may select the at least one SR configuration, for example, basedon the logical channel with the highest priority being mapped to the atleast one SR configuration, the wireless device falling back to the SRtransmission, and/or configured for an active uplink BWP of the cell) tosend (e.g., transmit) the uplink request (e.g., BFRQ). The base stationmay send (e.g., transmit) an uplink grant in time, for example, based onreceiving the uplink request via the at least one selected uplinkphysical channel associated with the logical channel with the highestpriority. This may increase speed of the BFR procedure.

The determining (e.g., selecting) may be based on a first-timeopportunity. A BFRQ transmission occasion occurring first in time (onthe one uplink BWP) may be associated with at least one SR configurationof the one or more SR configurations, for example, based on afirst-in-time opportunity and/or the BFRQ pending. The wireless devicemay select the at least one SR configuration to send (e.g., transmit)the uplink request (e.g., BFRQ), for example, based on the first-in-timeBFRQ transmission occasion being associated with the at least one SRconfiguration and/or the wireless device falling back to the SRtransmission. Determining (e.g., selecting) the first-in-timeopportunity may decrease latency for the BFR procedure.

Determining (e.g., selecting) an opportunity may be based on a maximumallowable SR transmission. The wireless device may select at least oneSR configuration of the one or more SR configurations, for example,based on the maximum allowable SR transmission and/or the BFRQ pending.The at least one SR configuration may have the lowest maximum quantityof SR transmissions. The wireless device may select the at least one SRconfiguration to send (e.g., transmit) the uplink request (e.g., BFRQ),for example, based on the at least one SR configuration having thelowest maximum quantity of SR transmissions and/or the wireless devicefalling back to the SR transmission.

At least one secondary cell of the one or more secondary cells may beactive. The wireless device may perform a BFR procedure of the at leastone secondary cell of the first cell. The wireless device may send(e.g., transmit) a BFRQ via at least one uplink physical channel of theone or more first uplink physical channels of the first cell. The basestation may avoid falling back to the SR transmission, for example, byconfiguring at least one uplink physical channel resource (e.g., PUCCHresource(s)) of the one or more first uplink physical channels (e.g.,indicated by the BFRQ configuration) of one or more uplink BWPs of thefirst plurality of UL BWPs of the first cell. The wireless device maynot expect to be configured with an uplink BWP of the first plurality ofUL BWPs of the first cell, for example, based on the uplink BWP notcomprising at least one uplink physical channel resource (e.g., PUCCHresource(s)) of the one or more first uplink physical channels.

FIG. 27 shows an example of timing of a downlink BFR procedure for asecondary cell. The wireless device may receive one or moreconfiguration parameters at time T₀. The wireless device may detect abeam failure of the second downlink BWP (e.g., DL-BWP-3 2512 in FIG.25A) of the second cell at time T₁ 2702. The wireless device may send(e.g., transmit) an initial transmission (e.g., BFRQ or SR) via thevalid at least one uplink physical channel (e.g., BFRQ or SR) of thefirst uplink BWP of the first cell for the BFR procedure of the seconddownlink BWP at time T₂ 2704. The wireless device may start the prohibittimer, for example, based on the sending the initial transmission (e.g.,BFRQ or SR). The wireless device may increment the transmission counter(e.g., BFRQ_COUNTER or SR_COUNTER) by one, for example, based on thesending of the initial transmission (e.g., BFRQ or SR).

The wireless device may switch an active uplink BWP of the first cellfrom the first uplink BWP (e.g., UL-BWP-1 2504 in FIG. 25A) to a seconduplink BWP (e.g., UL-BWP-2 2506 in FIG. 25A) of the first plurality ofUL BWPs of the first cell at time T₃ 2706. The switching may beperformed in response to receiving DCI (e.g., uplink grant) indicatingthe second uplink BWP. The switching may be performed in response toreceiving an RRC message indicating the second uplink BWP. The wirelessdevice may reset the transmission counter and/or the prohibit timer.

The one or more configuration parameters may indicate a first BWPinactivity timer of the first cell. The switching may be performed, forexample, based on an expiry of the first BWP inactivity timer of thefirst cell. The wireless device may operate in an unpaired spectrum(e.g., time division duplex (TDD)). The wireless device may switch anactive uplink BWP of the first cell, for example, based on the first BWPinactivity timer expiring and/or operating via the unpaired spectrum.The wireless device may switch an active uplink BWP of the first cell,for example, based on the first BWP inactivity timer expiring and/or aBWP linkage (e.g., UL-DL BWP linkage due to BFR procedure).

The wireless device may determine that at least one uplink physicalchannel resource (e.g., PUCCH resource for the BFRQ or SR) of the one ormore first uplink physical channels (e.g., indicated by the BFRQconfiguration or SR configuration) is not configured for the (switched)second uplink BWP (e.g., UL-BWP-2 2506 in FIG. 25A). The wireless devicemay fall back to an SR transmission, for example, based on thedetermining that at least one uplink physical channel resource of theone or more first uplink physical channels is not configured for thesecond uplink BWP. The wireless device may reset the prohibit timerand/or the transmission counter (e.g., BFRQ_COUNTER or SR_COUNTER), forexample, based on falling back to the SR transmission.

The wireless device may determine that at least one second uplinkphysical channel (e.g., SR of UL-BWP-2 2506 in FIG. 25A) of the one ormore second uplink physical channels (e.g., indicated by the SRconfiguration) is configured for the second uplink BWP of the firstcell. The wireless device may fall back to an SR transmission, forexample, based on the determining that at least one second uplinkphysical channel of the one or more second uplink physical channels isconfigured for the second uplink BWP of the first cell. The wirelessdevice may reset the prohibit timer and/or the transmission counter(e.g., BFRQ_COUNTER or SR_COUNTER), for example, based on the fallingback to the SR transmission.

The wireless device may send (e.g., transmit) at time T₄ 2708 an uplinkrequest (e.g., the BFRQ, and/or SR) via valid at least one second uplinkphysical channel of the one or more second uplink physical channels(e.g., indicated by the SR configuration) for the BFR procedure of thesecond downlink BWP of the second cell, for example, based on fallingback to the SR transmission. The wireless device may start an SRprohibit timer, for example, based on the sending (e.g., transmitting)the uplink request. The wireless device may increment an SR transmissioncounter (e.g., SR_COUNTER) by one, for example, based on sending theuplink request. The SR configuration may indicate the SR prohibit timerand the SR transmission counter (e.g., SR_COUNTER). The valid at leastone second uplink physical channel may be on the one uplink BWP (e.g.,UL-BWP-2) of the cell (e.g., the first cell).

The wireless device may send (e.g., transmit) an uplink request (e.g.,BFRQ, SR) via valid at least one second uplink physical channel of theone or more second uplink physical channels for the BFR procedure of thesecond downlink BWP of the second cell, for example, based on the seconduplink BWP (e.g., UL-BWP-2 2506 in FIG. 25B) of the first cell isactive. The wireless device may start the SR prohibit timer, forexample, based on the sending the uplink request. The wireless devicemay increment an SR transmission counter (e.g., SR_COUNTER) by one, forexample, based on the sending (e.g., transmitting) the uplink request.

The wireless device may switch an active uplink BWP of the first cellfrom the second uplink BWP (e.g., UL-BWP-2 2506 in FIG. 25B) to thefirst uplink BWP (e.g., UL-BWP-1 2504 in FIG. 25B) during the BFRprocedure of the second downlink BWP of the second cell. The switchingmay be autonomously performed by the wireless device, for example, basedon a determination that no uplink resources exist for the BFRQ usingdedicated uplink BFR resources or SR resources. The switching may beautonomously performed by the wireless device, for example, based on adetermination that a second uplink BWP may be configured with the uplinkresources for the BFR procedure. The switching may be performed inresponse to receiving a DCI (e.g., uplink grant) indicating the firstuplink BWP. The switching may be performed in response to receiving anRRC message indicating the first uplink BWP.

The wireless device may determine that at least one uplink physicalchannel resource (e.g., PUCCH resource for the BFRQ) of the one or morefirst uplink physical channels (e.g., indicated by the BFRQconfiguration) is configured for the first uplink BWP. The wirelessdevice may reset the SR transmission counter (e.g., SR_COUNTER), forexample, based on the determining that the at least one uplink physicalchannel resource of the one or more first uplink physical channels isconfigured for the first uplink BWP. The wireless device may reset theSR prohibit timer, for example, based on the determining that the atleast one uplink physical channel resource of the one or more firstuplink physical channels is configured for the first uplink BWP.

The wireless device may fall back to a BFRQ transmission, for example,based on the determining that the at least one uplink physical channelresource of the one or more first uplink physical channels is configuredfor the first uplink BWP. The falling back to the BFRQ transmission maycomprise stopping the sending (e.g., transmitting) the uplink requestvia the at least one second uplink physical channel and sending (e.g.,transmitting) a pending BFRQ via the at least one uplink physicalchannel of the first uplink BWP. The falling back to the BFRQtransmission may increase speed of the BFR procedure. The base stationmay recover the beam failure of the second cell in time to avoid orreduce transmission delays or call drop. The falling back to an SRtransmission may comprise stopping the sending (e.g., transmitting) theBFRQ via the at least one uplink physical channel and/or sending (e.g.,transmitting) an uplink request (e.g., BFRQ, SR) via the at least onesecond uplink physical channel.

The wireless device may stop the sending (e.g., transmitting) the uplinkrequest, for example, based on the determining that the at least oneuplink physical channel resource of the one or more first uplinkphysical channels is configured for the first uplink BWP. The wirelessdevice may send (e.g., transmit) a BFRQ via the valid at least oneuplink physical channel of the first uplink BWP of the first cell forthe BFR procedure of the second downlink BWP of the second cell, forexample, based on the stopping. The wireless device may start theprohibit timer, for example, based on sending the BFRQ. The wirelessdevice may increment the BFRQ transmission counter (e.g., BFRQ_COUNTER)by one, for example, based on sending the BFRQ. The one of moreconfiguration parameters may comprise a first BWP inactivity timer forthe first cell. The wireless device may stop the first BWP inactivitytimer of the first cell, for example, based on initiating a BFRprocedure associated with the second cell. The wireless device may stopthe first BWP inactivity timer of the first cell, for example, based ontriggering the BFRQ for a BFR procedure associated with the second cell.Stopping the first BWP inactivity timer may avoid BWP switching duringthe BFR procedure. Stopping the first BWP inactivity timer may avoidfalling back to an SR transmission.

The wireless device may determine that an active uplink BWP of the firstcell is configured with at least one uplink physical channel (e.g.,PUCCH resource for the BFRQ) of the one or more first uplink physicalchannels (e.g., indicated by the BFRQ configuration), for example, basedon the wireless device initiating the BFR procedure associated with thesecond cell and/or the wireless device triggering the BFRQ. The wirelessdevice may stop the first BWP inactivity timer of the first cell, forexample, based on the determining that an active uplink BWP of the firstcell is configured with at least one uplink physical channel of the oneor more first uplink physical channels. The wireless device may operatein an unpaired spectrum (e.g., TDD).

The wireless device may determine that an active uplink BWP of the firstcell is not configured with at least one uplink physical channelresource (e.g., PUCCH resource for the BFRQ) of the one or more firstuplink physical channels (e.g., indicated by the BFRQ configuration),for example, based on the wireless device initiating the BFR procedureassociated with the second cell or the wireless device triggering theBFRQ. The wireless device may not stop the first BWP inactivity timer ofthe first cell, for example, based on the determining that an activeuplink BWP of the first cell is not configured with at least one uplinkphysical channel resource of the one or more first uplink physicalchannels. The wireless device may operate in an unpaired spectrum (e.g.,TDD).

FIG. 28A and FIG. 28B show examples of BWP switching during a downlinkBFR procedure for a secondary cell. The wireless device may receive theone or more configuration parameters at time T0 2800. One or moreconfiguration parameters (e.g., the BFRQ configuration) may indicate oneor more first uplink physical channels of the first cell. The wirelessdevice may use the one or more first uplink physical channels for a BFRprocedure of at least one secondary cell (e.g., SCell-1 2812 and SCell-22814 in FIG. 28B) of the one or more secondary cells. The wirelessdevice may activate the at least one secondary cell at time T₁ 2802. Thewireless device may activate the at least one secondary cell in responseto receiving an SCell Activation/Deactivation MAC CE activating the atleast one secondary cell.

The wireless device may not activate one or more cells of the at leastone secondary cell simultaneously (e.g., at the same time). The wirelessdevice may activate SCell-1 2812 at time slot n and may activate SCell-22814 at time slot n+k, k>=0. The wireless device may not deactivate oneor more cells of the at least one secondary cell simultaneously (e.g.,at the same time). The wireless device may deactivate SCell-1 2812 attime slot n and may deactivate SCell-2 2814 at time slot n+k, k>=0.

The wireless device may use the one or more first uplink physicalchannels for the BFR procedure of the at least one secondary cell, forexample, based on the at least one secondary cell being active. Thewireless device may send (e.g., transmit) a BFRQ via at least one uplinkphysical channel of the one or more first uplink physical channels forthe BFR procedure of the at least one secondary cell, for example, basedon the wireless device detects a beam failure on the at least onesecondary cell. The at least one uplink physical channel may beconfigured for an active uplink BWP of the first cell (e.g., UL-BWP-12803 in FIG. 28B).

The wireless device may deactivate the at least one secondary cell attime T₂ 2804. The wireless device may deactivate the at least onesecondary cell in response to receiving an SCell Activation/DeactivationMAC CE deactivating the at least one secondary cell. The wireless devicemay deactivate the at least one secondary cell in response to an expiryof sCellDeactivationTimer associated with the at least one secondarycell. The one or more configuration parameters may indicate thesCellDeactivationTimer timer.

The wireless device may not use the one or more first uplink physicalchannels for the BFR procedure of the deactivated at least one secondarycell, for example, based on the at least one secondary cell beingdeactivated. The wireless device may not send (e.g., transmit) a BFRQvia at least one uplink physical channel of the one or more first uplinkphysical channels for the BFR procedure of the at least one secondarycell, for example, based on the at least one secondary cell beingdeactivated. This deactivated secondary cell may result in a waste ofresources.

The wireless device may use the one or more first uplink physicalchannels for requesting uplink shared resources (e.g., UL-SCHresource(s)) for an uplink transmission, for example, based ondeactivating the at least one secondary cell. The base station may beinformed of the request for UL-SCH resources, for example, based on thebase station receiving an SR via at least one uplink channel resource(e.g., PUCCH resource) of the one or more first uplink channels (e.g.,BFRQ of UL-BWP-1 2803). The base station may distinguish that the SR isnot for a BFR procedure because the at least one secondary cell isdeactivated. The wireless device may clear the one or more first uplinkphysical channels, for example, based on deactivating the at least onesecondary cell.

The wireless device may trigger an SR for an uplink data. The SR may bepending. The wireless device may not have valid at least one seconduplink channel resource (e.g., PUCCH resource) of the one or more seconduplink channels (e.g., indicated by the SR configuration) to send theSR. The wireless device may have at least one uplink channel resource(e.g., PUCCH resource) of the one or more first uplink channels of anactive uplink BWP of the first cell (e.g., BFRQ of UL-BWP-1 2803). Theat least one secondary cell may be active, for example, based on the SRpending. The wireless device may initiate a random access procedure, forexample, based on the wireless device not having the valid at least onesecond uplink physical channel, having the valid at least one uplinkphysical channel (e.g., indicated by the BFRQ configuration) and/or theat least one secondary cell being active. The wireless device may cancelthe SR in response to the initiating.

The wireless device may not have at least one second uplink channelresource (e.g., PUCCH resource) of the one or more second uplinkchannels (e.g., indicated by the SR configuration) to send the SR. Thewireless device may have at least one uplink channel resource (e.g.,PUCCH resource) of the one or more first uplink channels of an activeuplink BWP of the first cell (e.g., BFRQ of UL-BWP-1 2803). The at leastone secondary cell may be deactivated, for example, based on the SRpending.

The wireless device may send (e.g., transmit) the SR via the at leastone uplink physical channel (e.g., PUCCH resource), for example, basedon the wireless device not having the at least one second uplinkphysical channel, having the valid at least one uplink physical channel(e.g., indicated by the BFRQ configuration), and/or the at least onesecondary cell being deactivated. The SR configuration may indicate oneor more second uplink physical channels.

The SR configuration may comprise a field indicating whether the one ormore second uplink physical channels associated with the SRconfiguration can be used for a BFR procedure of at least one secondarycell of the one or more secondary cells. The wireless device may use theone or more second uplink physical channels for a BFR procedure, forexample, based on a value of the field being 1 (or any other value). Thewireless device may not use the one or more second uplink physicalchannels for a BFR procedure, for example, based on a value of the fieldbeing 0 (or any other value). The wireless device may use the one ormore second uplink physical channels for a BFR procedure, for example,based on a value of the field indicating an enabled state. The wirelessdevice may not use the one or more second uplink physical channels for aBFR procedure, for example, based on a value of the field indicating anon-enabled and/or disabled state. The wireless device may use the oneor more second uplink physical channels for a BFR procedure, forexample, based on a value of the field indicating a “Yes” or anypositive or affirmative indication. The wireless device may not use theone or more second uplink physical channels for a BFR procedure, forexample, based on a value of the field indicating a “No” or any negativeor non-affirmative indication. The wireless device may use the one ormore second uplink physical channels for a BFR procedure, for example,based on the SR configuration comprising the field. The wireless devicemay not use the one or more second uplink physical channels for a BFRprocedure, for example, based on the SR configuration not comprising thefield.

The base station may configure at least one SR configuration of the oneor more SR configurations with the field. The wireless device may selectan SR configuration among at least one SR configuration in response tothe base station configuring the at least one SR configuration with thefield, for example, based on the wireless device falling back to an SRtransmission.

A wireless device may detect a beam failure for a downlink BWP a cell.The one or more configuration parameters may indicate a cell index ofthe cell (e.g., provided by a higher layer parameter servCellIndex). TheDL BWP may be indicated (e.g., identified) with a DL BWP index (e.g.,provided by a parameter such as higher layer parameter bwp-ID in the oneor more configuration parameters). The wireless device may determine(e.g., select, indicate, and/or identify) a candidate RS associated witha candidate RS index (e.g., provided by a parameter such as higher layerparameter in the one or more configuration parameters), for example,based on detecting the beam failure. The wireless device may determine(e.g., select, indicate and/or identify) the candidate RS through acandidate beam selection. The wireless device may send (e.g., transmit)a BFR MAC CE for a BFR procedure of the DL BWP of the cell. The BFR MACCE may comprise one or more fields. The one or more fields may compriseat least one of: a first field indicating the cell index of the cell, asecond field indicating the candidate RS index, and/or a third fieldindicating the downlink BWP index. The base station may be informed ofthe BFR procedure of the downlink BWP of the cell and the candidate RS,for example, based on receiving the BFR MAC CE. The base station mayreconfigure (e.g., by a parameter such as higher layer TCI parameter(e.g., TCI-StatesPDCCH-ToAddlist and/or TCI-StatesPDCCH-ToReleaseList orUE-specific PDCCH MAC CE)) DL control channels of the DL BWP of thecell.

The wireless device may detect a beam failure of the second downlink BWPof the second cell. The wireless device may initiate a BFR procedure forthe second downlink BWP, for example, based on or in response to thedetecting the beam failure of the second downlink BWP. The wirelessdevice may initiate the candidate beam selection for the BFR procedurefor the second downlink BWP. The candidate beam selection may comprisedetermining (e.g., selecting, indicating, and/or identifying) thecandidate RS (e.g., CSI-RS, SS/PBCH blocks) in the one or more secondcandidate RSs (e.g., candidateBeamRSList) of the second downlink BWP.The candidate RS may be associated with a candidate RS index (e.g.,periodic CSI-RS configuration indexes and/or the SSB indexes provided bythe one or more configuration parameters). The wireless device may havean uplink grant, for example, based on the wireless device detecting thebeam failure. The wireless device may have an uplink grant, for example,based on the wireless device initiating the BFR procedure. The wirelessdevice may have an uplink grant, for example, based on the BFRQ beingtriggered. The wireless device may have an uplink grant, for example,based on the wireless device selects/identifies the candidate RS for theBFR procedure.

The wireless device may send (e.g., transmit) a BFR MAC-CE to the basestation for the BFR procedure for the second downlink BWP, for example,based on having the uplink grant. The wireless device may send (e.g.,transmit) the BFR MAC CE via one or more uplink resources (e.g., PUSCHresource(s)) indicated by the uplink grant. The BFR MAC-CE may compriseone or more fields. The one or more fields may comprise at least one of:a first field indicating the second cell index, a second fieldindicating the candidate RS index, and/or a third field indicating thesecond downlink BWP index. The wireless device may not have an uplinkgrant, for example, based on the wireless device detecting the beamfailure. The wireless device may not have an uplink grant, for example,based on the wireless device initiating the BFR procedure. The wirelessdevice may not have an uplink grant, for example, based on the BFRQbeing triggered. The wireless device may not have an uplink grant, forexample, based on the wireless device determining (e.g., selectingand/or identifying) the candidate RS for the BFR procedure. The wirelessdevice may not send (e.g., transmit) the BFR MAC CE to the base station,for example, based not having the uplink grant.

The wireless device may send the BFRQ to the base station for the BFRprocedure, for example, based on not having the uplink grant. The BFRQmay be pending. The wireless device may send the BFRQ via at least oneuplink channel of the one or more first uplink channels. The at leastone uplink channel may be of an active uplink BWP of the first cell. Thewireless device may send an uplink request (e.g., BFRQ) via at least oneuplink channel resource (e.g., PUCCH resource) of one or more (e.g.,first or second) uplink channels in response to the initiating the BFRprocedure for the second downlink BWP of the second cell.

The wireless device may start a timer (e.g., ra-responseWindow,sr-prohibit timer, bfrq-prohibit timer, prohibit timer) for a BFRresponse from the base station in response to the sending the uplinkrequest. The wireless device may monitor at least one downlink controlchannel (e.g., of the first cell), for the BFR response from the basestation, while the timer is running. The BFR response may comprise a DCIindicating an uplink grant (e.g., for the second cell). The BFR responsemay comprise a DCI indicating a downlink assignment (e.g., for thesecond cell). The wireless device may send (e.g., transmit) the BFRQ viaat least one uplink physical channel of the one or more second uplinkphysical channels.

The wireless device may send (e.g., transmit) the BFRQ via at least oneuplink physical channel (e.g., PUCCH) of the one or more first uplinkphysical channels of the first cell, for example, based on initiatingBFR procedure for the second downlink BWP of the second cell,determining (e.g., selecting, indicating, and/or identifying) thecandidate RS, and/or the wireless device not having an uplink grant. Thewireless device may send (e.g., transmit) the pending BFRQ via at leastone uplink channel resource (e.g., PUCCH resource) of the one or morefirst uplink channels of the first cell, for example, based oninitiating BFR procedure for the second downlink BWP of the second cell,determining (e.g., selecting, indicating, and/or identifying) thecandidate RS, and/or the wireless device not having an uplink grant. Thewireless device may send (e.g., transmit) the BFRQ to request an uplinkgrant (e.g., UL-SCH resource(s)) to send (e.g., transmit) the BFR MACCE. The wireless device may receive an uplink grant from the basestation. The base station may send (e.g., transmit) an uplink grant tothe wireless device, for example, based on or in response to receivingthe BFRQ via the at least one uplink physical channel.

The wireless device may send (e.g., transmit) a BFR MAC CE to the basestation for the BFR procedure for the second downlink BWP, for example,based on receiving the uplink grant. The wireless device may send (e.g.,transmit) the BFR MAC CE via one or more PUSCH resources indicated bythe uplink grant. The BFR MAC-CE may comprise one or more fields. Theone or more fields may comprise at least one of: a first fieldindicating the second cell index, a second field indicating thecandidate RS index, and/or a third field indicating the second downlinkBWP index. The wireless device may monitor for a BFR response from thebase station, for example, based on the sending (e.g., transmitting) theBFR MAC CE.

The wireless device may send (e.g., transmit) a MAC PDU, for example,based on receiving the uplink grant. The MAC PDU may comprise the BFRMAC-CE for the BFR procedure for the second downlink BWP. The wirelessdevice may cancel the pending BFRQ, for example, based on or in responseto the MAC PDU comprising the BFR MAC-CE. The wireless device maysuccessfully perform the BFR procedure for the second downlink BWP ofthe second cell in response to the sending (e.g., transmitting) the MACPDU comprising the BFR MAC-CE.

The wireless device may receive an acknowledgement message (ACK) for theBFR MAC CE as the BFR response. The receiving the ACK for the BFR MAC CEmay ensure that the base station received the BFR MAC CE message. Thewireless device may successfully perform the BFR procedure for thesecond downlink BWP of the second cell, for example, based on or inresponse to receiving the ACK for the BFR MAC-CE.

The BFR response may be a TCI parameter (e.g., a higher layer TCIparameter such as TCI-StatesPDCCH-ToAddlist and/orTCI-StatesPDCCH-ToReleaseList). The wireless device may receive the TCIparameter for the second cell. The TCI parameter may comprise one ormore TCI states for the second cell. The wireless device maysuccessfully perform the BFR procedure for the second downlink BWP ofthe second cell, for example, based on receiving the TCI parameter.

The wireless device may receive a MAC CE activation command (e.g.,UE-specific PDCCH MAC CE) indicating a TCI state of the one or more TCIstates for the second cell. The wireless device may successfully performthe BFR procedure for the second downlink BWP of the second cell, forexample, based on receiving the MAC CE activation command.

The BFR response may be a MAC CE activation command (e.g., UE-specificPDCCH MAC CE) indicating a TCI state for the second cell. The wirelessdevice may receive the MAC CE activation command for the second cell.The wireless device may successfully perform the BFR procedure for thesecond downlink BWP of the second cell, for example, based on receivingthe MAC CE activation command.

The TCI state may be used for at least one downlink control resource(e.g., PDCCH resource) reception in a coreset of the second downlink BWPof the second cell. The TCI state may indicate quasi co-locationinformation of DM-RS antenna port for the at least one downlink controlresource (e.g., PDCCH resource) reception in the coreset. The TCI statemay indicate that the DM-RS antenna port for the at least one downlinkcontrol resource (e.g., PDCCH resource) reception in the coreset isquasi co-located (e.g., QCL-TypeD) with one or more downlink RSs (e.g.,the candidate RS) indicated by the TCI state. The wireless device mayreset the BFI_COUNTER to zero, one or any other quantity, for examplebased on completing the BFR procedure for the second downlink BWP of thesecond cell.

FIG. 29 shows an example of a downlink BFR procedure of a secondarycell. A wireless device may avoid initiating a random access procedure,based on BFRQ and/or SR resources being configured for use of thewireless device. In step 2900, the wireless device may receive an RRCconfiguration for BFR and/or BFRQ. In step 2902, the wireless devicetriggers a BFRQ, for example, based on detecting a beam failure. In step2904, the wireless device may determine whether uplink resources (e.g.,PUCCH) are or were configured for BFRQ transmission of an active UL BWPof the first cell. In step 2910, the wireless device may send (e.g.,transmit) the BFRQ via one of the uplink resources (e.g., PUCCHresource(s)), for example, based on a “yes” determination in step 2904.In step 2906, the wireless device may determine whether uplink resources(e.g., PUCCH) were configured for SR transmission on an active UL BWP ofthe first cell, for example, based on a “no” determination in step 2904.In step 2912, the wireless device may send (e.g., transmit) the BFRQ viaone of the uplink resources (e.g., PUCCH resource(s)) allocated for SR,for example, based on a “yes” determination in step 2906. In step 2908,the wireless device may initiate a random access procedure and/or cancelthe BFRQ, for example, based on a “no” determination in step 2906.

The wireless device may receive, from a base station, one or moremessages. The one or more messages may comprise one of moreconfiguration parameters of a first cell and a second cell.

The one or more configuration parameters may comprise a BFRQconfiguration. The BFRQ configuration may comprise one or more firstuplink channels (e.g., PUCCH resource(s)) of the first cell. The basestation may configure the one or more first uplink physical channels fora BFR procedure of the second cell. The wireless device may send (e.g.,transmit) via the one or more first uplink physical channels for the BFRprocedure of the second cell.

The one or more configuration parameters may indicate one or more RSs ofthe second cell. The one or more RSs may comprise one or more CSI-RSsand/or one or more SSB/PBCHs. The wireless device may assess the one ormore RSs for a beam failure detection of the second cell. The one ormore configuration parameters may comprise a SR configuration. The SRconfiguration may comprise one or more second uplink physical channels(e.g., PUCCH resource(s)). The one or more configuration parameters mayfurther indicate a beam failure instance counter (e.g.,beamFailureInstanceMaxCount). The one or more configuration parametersmay indicate a first threshold (e.g., rlmInSyncOutOfSyncThreshold) forthe beam failure detection of the second cell. The first threshold maybe based on signal quality (e.g., hypothetical BLER, or L1-RSRP, orRSRQ, or SINR).

The wireless device may detect a beam failure of the second cell basedon the one or more RSs. The wireless device may determine a quantity ofbeam failure instance (BFI) indication associated with the second cellreaching to the BFI counter. The BFI indication may comprise assessingthe one or more RSs of the second cell with radio quality lower than thefirst threshold. The wireless device may detect the beam failure of thesecond cell, for example, based on determining the quantity of beamfailure instance indications associated with the second cell BFIcounter. The wireless device may trigger a BFRQ for the BFR procedure ofthe second cell, for example, based on detecting the beam failure of thesecond cell based on the one or more RSs.

The wireless device may determine that an active uplink BWP of the firstcell is not configured with at least one uplink channel (e.g., PUCCHresource(s) for BFRQ transmission) of the one or more first uplinkchannels. The wireless device may send (e.g., transmit) the BFRQ via theone or more second uplink channels, for example, based on determiningthat an active uplink BWP of the first cell is not configured with atleast one uplink channel of the one or more first uplink channels. Theone or more second uplink channels may be configured for an uplink BWPof a cell. The cell may be the first cell. The cell may be differentfrom the first cell (e.g., the second cell, one or more secondarycells).

FIG. 30 shows an example of SCell BFR procedure using dedicated BFRresources. The wireless device may receive, at time T₀ 3000,configuration parameters that include BFR and/or BRFQ configurations forSR resources dedicated (e.g., allocated) for a BFR procedure. Thewireless device may initiate a BFR procedure for a secondary cell attime T₁ 3002, for example, based on determining (e.g., detecting) a beamfailure of a secondary cell. The wireless device may determine, betweenT₁ 3002 and T₂ 3004, that an uplink BWP of a first cell is configuredwith SR resources dedicated for the BFR procedure. The wireless devicemay send (e.g., transmit), at time T₂ 3004, a SR via the dedicated SRresources for the BFR procedure. A base station may become or be awareof the beam failure at and/or after time T₂ 3004, for example, based onreceiving the SR via the dedicated SR resources. The wireless device mayreceive, at time T₃ 3006, an uplink grant sufficient to send (e.g.,transmit) the BFR MAC CE. The wireless device may send (e.g., transmit),at time T₄ 3008) BFR MAC CE for the BFR procedure. The first cell may bePCell, PUCCH SCell, or may be the same as the secondary cell with thebeam failure.

FIG. 31 shows an example of SCell BFR procedure using SR resources. Thewireless device may receive, at time T₀ 3100, configuration parametersthat include an SR configuration, but lack BFR and/or BRFQconfigurations for SR resources dedicated (e.g., allocated) for a BFRprocedure. The wireless device may initiate a BFR procedure for asecondary cell at time T₁ 3102, for example, based on determining (e.g.,detecting) a beam failure of a secondary cell. The wireless device maydetermine, between T₁ 3102 and T₂ 3104, that an uplink BWP of a firstcell is not configured with SR resources dedicated for the BFRprocedure, but is configured with SR resources for requesting UL sharedresources (e.g., UL-SCH resource(s)). The wireless device may send(e.g., transmit), at time T₂ 3104, a SR via the SR resources for the BFRprocedure (e.g., SR resources that are not dedicated for BFR). Thewireless device may receive, at time T₃ 3106, an uplink grant that mayor may not be sufficient to send (e.g., transmit) the BFR MAC CE. Theuplink grant may or may not be enough to send BFR MAC CE, for example,based on the base station not being aware of the beam failure at time T₂3104. The wireless device may send the BFR MAC CE at time T₄ 3108, forexample, based on the uplink grant being sufficient to send BFR MAC CE.A base station may become or be aware of the beam failure at and/orafter time T₄ 3108, for example, based on receiving the BFR MAC CE.

FIG. 32 shows an example of SCell BFR procedure using an SRconfiguration with fields indicating dedicated SR resources for BFR. Awireless device may determine which dedicated (e.g., allocated) SRresources to use for BFR based on a SR configuration field for SRconfiguration. In step 3200, the wireless device may receiveconfiguration parameters for a plurality of SR configurations. Theconfiguration parameters may be for an active uplink BWP of a firstcell. In step 3202, the wireless device may initiate a BFR procedure fora secondary cell, for example, based on determining (e.g., detecting) abeam failure for a secondary cell. In step 3204, the wireless device maydetermine an SR configuration, among the plurality of SR configurations,for example, based on a field indicating that the SR configuration isfor the BFR procedure. In step 3206, the wireless device may send (e.g.,transmit), for the BFR procedure, an SR via a SR resource, for example,based on the SR configuration and/or a “yes” determination from step3204. In a step (not shown), the wireless device may cancel the BFRprocedure and perform a random access procedure, for example, based on a“no” determination from step 3204.

A wireless device may perform a method comprising multiple operations.The wireless device may receive, by a wireless device, configurationparameters indicating first uplink control channel resources, on a firstcell, for a beam failure recovery (BFR) procedure of a second cell; andsecond uplink control channel resources for requesting uplink sharedchannel resources. The wireless device may detect a beam failure of thesecond cell. The wireless device may determine that an active uplinkbandwidth part (BWP) of the first cell is not configured with the firstuplink control channel resources for the BFR procedure of the secondcell. The wireless device may determine that the active uplink BWP ofthe first cell is configured with the second uplink control channelresources. The wireless device may send, via the second uplink controlchannel resources, an uplink signal for the BFR procedure.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The wireless device may determine, based on a type of data fortransmission, the second uplink control channel resources. Theconfiguration parameters may comprise a first field indicating that ascheduling request (SR) configuration is for a BFR procedure of a cell;and a second field indicating one or more second uplink control channelresources for requesting uplink shared channel resources. The wirelessdevice may determine that the active uplink BWP of a cell is configuredwith at least one second uplink control channel comprising the seconduplink control channel resources. The wireless device may determine thata second active uplink BWP of the first cell is not configured with: atleast one first uplink control channel comprising the first uplinkcontrol channel resources; and at least one second uplink controlchannel comprising the second uplink control channel resources. Thewireless device may initiate a random access procedure. The wirelessdevice may determine, based on a highest logical channel priority, atleast one second uplink control channel resource. The wireless devicemay determine that a second active uplink BWP of the first cell isconfigured with at least one first uplink control channel comprising atleast one of the first uplink control channel resources. The wirelessdevice may send, via the at least one first uplink control channel, theuplink signal for the BFR procedure. The wireless device may increment aBFR transmission counter or starting a prohibit timer.

A wireless device may perform a method comprising multiple operations.The wireless device may initiate, based on detecting a beam failure of asecond cell, a beam failure recovery (BFR) procedure. The wirelessdevice may determine that an active uplink bandwidth part (BWP) of afirst cell is not configured with at least one first uplink controlchannel resource for the BFR procedure. The wireless device maydetermine, based on a type of data for transmission via an uplinkcontrol channel, at least one second uplink control channel resource forrequesting uplink shared channel resources for the BFR procedure. Thewireless device may send, via the second uplink control channelresources, an uplink signal for the BFR procedure.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The determining the at least one second uplink control channel resourcefor scheduling requests for the BFR procedure may comprise: determiningan uplink grant, based on a scheduling request via the at least onesecond uplink control channel resource, is sufficient to send a BFRmedium access control control element (BFR MAC CE). The determining theat least one second uplink control channel resource for schedulingrequests to use for the BFR procedure is based on at least one of: thetype of data being Ultra Reliable Low Latency Communications (URLLC);the type of data being enhanced Mobile Broadband (eMBB); a highestlogical channel priority of available uplink control resources; the atleast one second uplink control channel resource being first-in-time; orthe uplink control resource being associated with a largest uplink grantof available uplink control resources. The wireless device may receiveconfiguration parameters that comprise: a first field indicating that ascheduling request (SR) configuration is for a BFR procedure of a cell;and a second field indicating one or more second uplink control channelresources for requesting uplink shared channel resources. The wirelessdevice may switch the active uplink BWP to a second active uplink BWP ofthe first cell during the BFR procedure, wherein the second activeuplink BWP is configured with at least one second uplink control channelresource for the BFR procedure. The wireless device may stop the sendingof the uplink signal via the at least one second uplink control channelresource. The wireless device may send, via the at least one seconduplink control channel resource, the uplink signal for the BFRprocedure. The wireless device may switch the active uplink BWP to asecond active uplink BWP of the first cell during the BFR procedure,wherein the second active uplink BWP is configured with at least onesecond uplink control channel resource for the BFR procedure. Thewireless device may reset a scheduling request transmission counter or aprohibit timer. The wireless device may start transmitting, via the atleast one second uplink control channel resource, the uplink signal forthe BFR procedure. The at least one second uplink control channelresource may be a scheduling request resource.

A wireless device may perform a method comprising multiple operations.The wireless device may initiate, based on detecting a beam failure of asecond cell, a beam failure recovery (BFR) procedure. The wirelessdevice may switch, during the BFR procedure, a first active uplinkbandwidth part (BWP) of a first cell to a second active uplink BWP ofthe first cell, wherein the second active uplink BWP is configured withat least one uplink control channel comprising first uplink controlchannel resources for requesting the BFR procedure of the second cell.The wireless device may reset a scheduling request transmission counteror a prohibit timer. The wireless device may send, via the first uplinkcontrol channel resources, an uplink signal for the BFR procedure.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The wireless device may stop the sending of the uplink signal via thefirst uplink control channel resources of the first active BWP. Thewireless device may receive, based on the uplink signal, an uplinkgrant. The wireless device may determine that an active uplink BWP ofthe first cell is not configured with at least one first uplink controlchannel resource for a BFR procedure. The wireless device may send, viaat least one second uplink control channel and using at least one seconduplink control channel resource for requesting uplink shared channelresources, an uplink signal for the BFR procedure. The wireless devicemay determine, based on a type of data for transmission via the uplinkcontrol channel, the first uplink control channel resources. Thewireless device may receive configuration parameters that comprise: afirst field indicating that a scheduling request (SR) configuration isfor a BFR procedure of a cell; and a second field indicating one or moresecond uplink control channel resources for requesting uplink sharedchannel resources.

A wireless device may perform a method comprising multiple operations.The wireless device may receive, by a wireless device, one or moremessages comprising configuration parameters indicating: first uplinkcontrol channel resources, on a first cell, for a beam failure recovery(BFR) procedure of a second cell; and second uplink control channelresources for requesting uplink shared channel resources. The wirelessdevice may initiate, based on detecting a beam failure of the secondcell, the BFR procedure. The wireless device may determine that anactive uplink bandwidth part (BWP) of the first cell is not configuredwith at least one first uplink control channel of the first uplinkcontrol channel resources. The wireless device may transmit, based onthe determining and via at least one second uplink control channel ofthe second uplink control channel resources, an uplink signal for theBFR procedure.

The wireless device may also perform one or more additional operationsor include additional elements in conjunction with the described method.The wireless device may trigger, based on the detecting the beamfailure, a scheduling request for the BFR procedure. The uplink signalmay comprise the scheduling request. The wireless device may determinethat the active uplink BWP of the first cell is configured with the atleast one second uplink control channel. The wireless device maydetermine that an active uplink BWP of a cell, of the wireless device,is configured with the at least one second uplink control channel,wherein the cell is different from or the same as the first cell. Thewireless device may determine that a second active uplink BWP of thefirst cell is not configured with: at least one first uplink controlchannel of the first uplink control channel resources; and at least onesecond uplink control channel of the second uplink control channelresources. The wireless device may initiate, based on the determining, arandom-access procedure for the BFR procedure. The wireless device maydetermine that: a second active uplink BWP of the first cell is notconfigured with at least one first uplink control channel of the firstuplink control channel resources; and an active uplink BWP of a cell, ofthe wireless device, is not configured with at least one second uplinkcontrol channel of the second uplink control channel resources, whereinthe cell is different from or the same as the first cell. The wirelessdevice may initiate, based on the determining, a random-access procedurefor the BFR procedure. The wireless device may cancel, based on theinitiating the random-access procedure, the scheduling request. Thewireless device may keep, based on the initiating the random-accessprocedure, the scheduling request pending. The wireless device maytransmit, via a physical random-access channel resource, a random-accesspreamble for the BFR procedure. The one or more configuration parametersmay comprise or indicate one or more scheduling request configurationsindicating the second uplink control channel resources. The wirelessdevice may select at least one scheduling request configuration, amongthe one or more scheduling request configurations, indicating the atleast one second uplink control channel. The wireless device may selectat least one scheduling request configuration with a highest logicalchannel priority among logical channel priorities of the one or morescheduling request configurations. The wireless device may select, whenthe scheduling request is pending, at least one scheduling requestconfiguration with a transmission occasion occurring first in time amongtransmission occasions of the one or more scheduling requestconfigurations. The wireless device may select at least one schedulingrequest configuration with a lowest maximum allowable scheduling requesttransmission among maximum allowable scheduling request transmissions ofthe one or more scheduling request configurations. The wireless devicemay determine that a second active uplink BWP part of the first cell isconfigured with at least one first uplink control channel of the firstuplink control channel resources. The wireless device may, transmit,based on the determining and via the at least one first uplink controlchannel, the uplink signal for the BFR procedure. The wireless devicemay, based on the transmitting the uplink signal: increment a BFRtransmission counter or start a prohibit timer. The wireless device may,based on switching the second active uplink BWP to a third active uplinkBWP of the first cell during the BFR procedure, wherein the third activeuplink BWP is not configured with at least one first uplink controlchannel of the first uplink control channel resources, resetting: theBFR transmission counter; or the prohibit timer. The third active uplinkBWP may not be configured with at least one second uplink controlchannel of the second uplink control channel resources. The wirelessdevice may, based on the transmitting the uplink signal, increment ascheduling request transmission counter or start a prohibit timer. Thewireless device may, based on switching the active uplink BWP to a thirdactive uplink BWP of the first cell during the BFR procedure, whereinthe third active uplink BWP is configured with at least one first uplinkcontrol channel of the first uplink control channel resources. Thewireless device may reset the scheduling request transmission counter orthe prohibit timer. The wireless device may stop the transmitting of theuplink signal via the at least one second uplink control channel. Thewireless device may start transmitting, via the at least one firstuplink control channel, the uplink signal for the BFR procedure. Thewireless device may stop, based on the initiating the BFR procedure, aBWP inactivity timer of the first cell. The wireless device may stop,based on the triggering the scheduling request for the BFR procedure, aBWP inactivity timer of the first cell. The wireless device maydeactivate the second cell. The wireless device may transmit, based onthe deactivating the second cell and via the at least one first uplinkcontrol channel, a scheduling request for requesting uplink sharedchannel resources. The second cell may be in an active state. Thewireless device may not transmit, based on the second cell being in anactive state and via the at least one first uplink control channel, ascheduling request for requesting uplink shared channel resources. Thewireless device may clear, based on the deactivating the second cell,the first uplink control channel resources. The second cell may operatein an unpaired spectrum. A scheduling request configuration of one ormore scheduling request configurations may comprise a field indicatingwhether at least one uplink control channel resource, of the seconduplink control channel resources, of the scheduling requestconfiguration is used for the BFR procedure of the second cell. The atleast one uplink control channel resource of the scheduling requestconfiguration being used for the BFR procedure of the second cell maycomprise that the wireless device transmits, via the at least one uplinkcontrol channel resource, the uplink signal for the BFR procedure of thesecond cell.

FIG. 33 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 120A and/or 120B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 3300 may include one ormore processors 3301, which may execute instructions stored in therandom access memory (RAM) 3303, the removable media 3304 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive3305. The computing device 3300 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 3301 andany process that requests access to any hardware and/or softwarecomponents of the computing device 3300 (e.g., ROM 3302, RAM 3303, theremovable media 3304, the hard drive 3305, the device controller 3307, anetwork interface 3309, a GPS 3311, a Bluetooth interface 3312, a WiFiinterface 3313, etc.). The computing device 3300 may include one or moreoutput devices, such as the display 3306 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 3307, such as a video processor. There mayalso be one or more user input devices 3308, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device3300 may also include one or more network interfaces, such as a networkinterface 3309, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 3309 may provide aninterface for the computing device 3300 to communicate with a network3310 (e.g., a RAN, or any other network). The network interface 3309 mayinclude a modem (e.g., a cable modem), and the external network 3310 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 3300 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 3311, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 3300.

The example in FIG. 33 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 3300 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 3301, ROM storage 3302, display 3306, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 33 .Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

What is claimed is:
 1. A method comprising: triggering, by a wirelessdevice and based on detection of a beam failure of a secondary cell, ascheduling request for beam failure recovery (BFR) of the secondarycell; and based on an active uplink bandwidth part (BWP) of a first cellhaving no valid physical uplink control channel (PUCCH) resource for thescheduling request: initiating, via the first cell, a random accessprocedure; and cancelling the scheduling request.
 2. The method of claim1, further comprising: based on the active uplink BWP of the first cellnot being configured with at least one uplink control channel resourcefor the scheduling request, determining that the active uplink BWP ofthe first cell has no valid PUCCH resource for the scheduling request.3. The method of claim 1, further comprising: receiving configurationparameters indicating: at least one first uplink control channelresource, of the first cell, for BFR of the secondary cell; and at leastone second uplink control channel resource for requesting at least oneuplink shared channel resource.
 4. The method of claim 1, furthercomprising: determining that a second active uplink BWP of the firstcell is configured with at least one uplink control channel resource;and sending, via the at least one uplink control channel resource, anuplink signal for BFR of the secondary cell.
 5. The method of claim 1,further comprising: switching the active uplink BWP to a second activeuplink BWP of the first cell during BFR of the secondary cell, whereinthe second active uplink BWP is configured with at least one uplinkcontrol channel resource for BFR of the secondary cell; and sending, viathe at least one uplink control channel resource, an uplink signal forBFR of the secondary cell.
 6. The method of claim 1, wherein theinitiating the random access procedure comprises sending, via the firstcell, a random access preamble.
 7. The method of claim 1, wherein thecancelling the scheduling request comprises cancelling the schedulingrequest while the scheduling request is pending.
 8. A wireless devicecomprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the wirelessdevice to: trigger, based on detection of a beam failure of a secondarycell, a scheduling request for beam failure recovery (BFR) of thesecondary cell; and based on an active uplink bandwidth part (BWP) of afirst cell having no valid physical uplink control channel (PUCCH)resource for the scheduling request: initiate, via the first cell, arandom access procedure; and cancel the scheduling request.
 9. Thewireless device of claim 8, wherein the instructions, when executed bythe one or more processors, cause the wireless device to: based on theactive uplink BWP of the first cell not being configured with at leastone uplink control channel resource for BFR of the secondary cell,determine that the active uplink BWP of the first cell has no validPUCCH resource for the scheduling request.
 10. The wireless device ofclaim 8, wherein the instructions, when executed by the one or moreprocessors, cause the wireless device to: receive configurationparameters indicating: at least one first uplink control channelresource, of the first cell, for BFR of the secondary cell; and at leastone second uplink control channel resource for requesting at least oneuplink shared channel resource.
 11. The wireless device of claim 8,wherein the instructions, when executed by the one or more processors,cause the wireless device to: determine that a second active uplink BWPof the first cell is configured with at least one uplink control channelresource; and send, via the at least one uplink control channelresource, an uplink signal for BFR of the secondary cell.
 12. Thewireless device of claim 8, wherein the instructions, when executed bythe one or more processors, cause the wireless device to: switch theactive uplink BWP to a second active uplink BWP of the first cell duringBFR of the secondary cell, wherein the second active uplink BWP isconfigured with at least one uplink control channel resource for BFR ofthe secondary cell; and send, via the at least one uplink controlchannel resource, an uplink signal for BFR of the secondary cell. 13.The wireless device of claim 8, wherein the instructions, when executedby the one or more processors, cause the wireless device to initiate therandom access procedure by sending, via the first cell, a random accesspreamble.
 14. The wireless device of claim 8, wherein the instructions,when executed by the one or more processors, cause the wireless deviceto cancel the scheduling request by cancelling the scheduling requestwhile the scheduling request is pending.
 15. A non-transitorycomputer-readable medium storing instructions that, when executed,configure a wireless device to: trigger, based on detection of a beamfailure of a secondary cell, a scheduling request for beam failurerecovery (BFR) of the secondary cell; and based on an active uplinkbandwidth part (BWP) of a first cell having no valid physical uplinkcontrol channel (PUCCH) resource for the scheduling request: initiate,via the first cell, a random access procedure; and cancel the schedulingrequest.
 16. The non-transitory computer-readable medium of claim 15,wherein the instructions, when executed, further configure the wirelessdevice to: based on the active uplink BWP of the first cell not beingconfigured with at least one uplink control channel resource for thescheduling request, determine that the active uplink BWP of the firstcell has no valid PUCCH resource for the scheduling request.
 17. Thenon-transitory computer-readable medium of claim 15, wherein theinstructions, when executed, further configure the wireless device to:receive configuration parameters indicating: at least one first uplinkcontrol channel resource, of the first cell, for BFR of the secondarycell; and at least one second uplink control channel resource forrequesting at least one uplink shared channel resource.
 18. Thenon-transitory computer-readable medium of claim 15, wherein theinstructions, when executed, further configure the wireless device to:determine that a second active uplink BWP of the first cell isconfigured with at least one uplink control channel resource; and send,via the at least one uplink control channel resource, an uplink signalfor BFR of the secondary cell.
 19. The non-transitory computer-readablemedium of claim 15, wherein the instructions, when executed, furtherconfigure the wireless device to: switch the active uplink BWP to asecond active uplink BWP of the first cell during BFR of the secondarycell, wherein the second active uplink BWP is configured with at leastone uplink control channel resource for BFR of the secondary cell; andsend, via the at least one uplink control channel resource, an uplinksignal for BFR of the secondary cell.
 20. The non-transitorycomputer-readable medium of claim 15, wherein the instructions, whenexecuted, further configure the wireless device to initiate the randomaccess procedure by sending, via the first cell, a random accesspreamble.
 21. The non-transitory computer-readable medium of claim 15,wherein the instructions, when executed, further configure the wirelessdevice to cancel the scheduling request by cancelling the schedulingrequest while the scheduling request is pending.
 22. A systemcomprising: a base station; and a wireless device, wherein the wirelessdevice is configured to: trigger, based on detection of a beam failureof a secondary cell, a scheduling request for beam failure recovery(BFR) of the secondary cell; and based on an active uplink bandwidthpart (BWP) of a first cell having no valid physical uplink controlchannel (PUCCH) resource for the scheduling request: initiate, via thefirst cell, a random access procedure; and cancel the schedulingrequest, and wherein the base station is configured to receive apreamble associated with the random access procedure.
 23. The system ofclaim 22, wherein the wireless device is further configured to: based onthe active uplink BWP of the first cell not being configured with atleast one uplink control channel resource for the scheduling request,determine that the active uplink BWP of the first cell has no validPUCCH resource for the scheduling request.
 24. The system of claim 22,wherein the base station is further configured to send configurationparameters indicating: at least one first uplink control channelresource, of the first cell, for BFR of the secondary cell; and at leastone second uplink control channel resource for requesting at least oneuplink shared channel resource.
 25. The system of claim 22, wherein thewireless device is further configured to: determine that a second activeuplink BWP of the first cell is configured with at least one uplinkcontrol channel resource; and send, via the at least one uplink controlchannel resource, an uplink signal for BFR of the secondary cell. 26.The system of claim 22, wherein the wireless device is furtherconfigured to: switch the active uplink BWP to a second active uplinkBWP of the first cell during BFR of the secondary cell, wherein thesecond active uplink BWP is configured with at least one uplink controlchannel resource for BFR of the secondary cell; and send, via the atleast one uplink control channel resource, an uplink signal for BFR ofthe secondary cell.
 27. The system of claim 22, wherein the wirelessdevice is further configured to initiate the random access procedure bysending, via the first cell, a random access preamble.
 28. The system ofclaim 22, wherein the wireless device is further configured to cancelthe scheduling request by cancelling the scheduling request while thescheduling request is pending.